From: Jani Nikula <jani.nikula@intel.com>
To: Danilo Krummrich <dakr@redhat.com>
Cc: nouveau@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/nouveau: include drm/drm_edid.h only where needed
Date: Wed, 10 Jan 2024 11:18:19 +0200 [thread overview]
Message-ID: <87frz5wnqc.fsf@intel.com> (raw)
In-Reply-To: <6f343c87-fbb4-4779-aced-2e0df7b18e63@redhat.com>
On Tue, 09 Jan 2024, Danilo Krummrich <dakr@redhat.com> wrote:
> On 1/9/24 10:59, Jani Nikula wrote:
>> On Mon, 08 Jan 2024, Danilo Krummrich <dakr@redhat.com> wrote:
>>> On 1/4/24 21:16, Jani Nikula wrote:
>>>> Including drm_edid.h from nouveau_connector.h causes the rebuild of 15
>>>> files when drm_edid.h is modified, while there are only a few files that
>>>> actually need to include drm_edid.h.
>>>>
>>>> Cc: Karol Herbst <kherbst@redhat.com>
>>>> Cc: Lyude Paul <lyude@redhat.com>
>>>> Cc: Danilo Krummrich <dakr@redhat.com>
>>>> Cc: nouveau@lists.freedesktop.org
>>>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>>
>>> Reviewed-by: Danilo Krummrich <dakr@redhat.com>
>>
>> Are you going to pick this up via the nouveau tree, or shall I apply it
>> to drm-misc-next?
>
> We don't maintain a separate tree, hence feel free to apply it to drm-misc-next.
Thanks for the review, pushed to drm-misc-next.
You do still have
T: git https://gitlab.freedesktop.org/drm/nouveau.git
MAINTAINERS entry, so I thought that's where you apply patches.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-01-10 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 20:16 [PATCH 1/3] drm/nouveau: include drm/drm_edid.h only where needed Jani Nikula
2024-01-05 9:59 ` Andi Shyti
2024-01-08 18:04 ` Danilo Krummrich
2024-01-09 9:59 ` Jani Nikula
2024-01-09 17:01 ` Danilo Krummrich
2024-01-10 9:18 ` Jani Nikula [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frz5wnqc.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dakr@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).