From: Jani Nikula <jani.nikula@intel.com>
To: Danilo Krummrich <dakr@redhat.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: nouveau@lists.freedesktop.org, Karol Herbst <kherbst@redhat.com>
Subject: Re: [PATCH 1/3] drm/nouveau: include drm/drm_edid.h only where needed
Date: Tue, 09 Jan 2024 11:59:52 +0200 [thread overview]
Message-ID: <87ttnmx1wn.fsf@intel.com> (raw)
In-Reply-To: <95f6815c-1ff5-4c89-b8c6-0445834a0083@redhat.com>
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?
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/nouveau/dispnv50/head.c | 1 +
>> drivers/gpu/drm/nouveau/nouveau_connector.h | 2 +-
>> 2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/nouveau/dispnv50/head.c b/drivers/gpu/drm/nouveau/dispnv50/head.c
>> index 5f490fbf1877..83355dbc15ee 100644
>> --- a/drivers/gpu/drm/nouveau/dispnv50/head.c
>> +++ b/drivers/gpu/drm/nouveau/dispnv50/head.c
>> @@ -32,6 +32,7 @@
>>
>> #include <drm/drm_atomic.h>
>> #include <drm/drm_atomic_helper.h>
>> +#include <drm/drm_edid.h>
>> #include <drm/drm_vblank.h>
>> #include "nouveau_connector.h"
>>
>> diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.h b/drivers/gpu/drm/nouveau/nouveau_connector.h
>> index a2df4918340c..0608cabed058 100644
>> --- a/drivers/gpu/drm/nouveau/nouveau_connector.h
>> +++ b/drivers/gpu/drm/nouveau/nouveau_connector.h
>> @@ -35,7 +35,6 @@
>>
>> #include <drm/display/drm_dp_helper.h>
>> #include <drm/drm_crtc.h>
>> -#include <drm/drm_edid.h>
>> #include <drm/drm_encoder.h>
>> #include <drm/drm_util.h>
>>
>> @@ -44,6 +43,7 @@
>>
>> struct nvkm_i2c_port;
>> struct dcb_output;
>> +struct edid;
>>
>> #ifdef CONFIG_DRM_NOUVEAU_BACKLIGHT
>> struct nouveau_backlight {
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-09 9:59 UTC|newest]
Thread overview: 16+ 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-04 20:16 ` [PATCH 2/3] drm/hisilicon: " Jani Nikula
2024-01-05 9:59 ` Andi Shyti
2024-01-04 20:16 ` [PATCH 3/3] ASoC: hdmi-codec: drop drm/drm_edid.h include Jani Nikula
2024-01-05 10:05 ` Andi Shyti
2024-01-05 16:04 ` Alex Deucher
2024-01-10 9:24 ` Jani Nikula
2024-01-12 13:26 ` [3/3] " Sarha, Jyri
2024-01-16 16:14 ` Jani Nikula
2024-01-04 23:28 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/nouveau: include drm/drm_edid.h only where needed Patchwork
2024-01-05 1:16 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-05 9:59 ` [PATCH 1/3] " Andi Shyti
2024-01-08 18:04 ` Danilo Krummrich
2024-01-09 9:59 ` Jani Nikula [this message]
2024-01-09 17:01 ` Danilo Krummrich
2024-01-10 9:18 ` Jani Nikula
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=87ttnmx1wn.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=kherbst@redhat.com \
--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