From: Maxime Ripard <mripard@kernel.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Daniel Stone <daniel@fooishbar.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
kernel@collabora.com
Subject: Re: [PATCH] drm/tests: Move test EDID data to separate .c file
Date: Wed, 10 Jun 2026 15:19:46 +0200 [thread overview]
Message-ID: <20260610-quantum-glossy-partridge-136d8b@houat> (raw)
In-Reply-To: <79f42f7e29b7a807c8ca4e622a547183018d65cb@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
On Wed, Jun 10, 2026 at 03:32:12PM +0300, Jani Nikula wrote:
> On Wed, 10 Jun 2026, Nicolas Frattaroli <nicolas.frattaroli@collabora.com> wrote:
> > Having the test EDID arrays defined in the .h directly will duplicate
> > them across every user of the EDID arrays. This works fine as long as
> > there's only one user, but may produce build warnings/errors when there
> > are multiple users and not all of them use all definitions.
> >
> > Move the array definitions to a new .c file, and mark the declarations
> > in the header as "extern" to avoid the linker throwing a fit, and give
> > them an explicit size (either 128 or 256, depending on EDID) to avoid
> > the compiler inferring that they must be size 1.
> >
> > Reported-by: Jani Nikula <jani.nikula@linux.intel.com>
> > Closes: https://lore.kernel.org/r/04ff70850213ae0f75486b1a27a7edb6fb4e71c3@intel.com/
> > Fixes: ce1d0139adac ("drm/tests: bridge: Add test for HDMI output bus formats helper")
> > Fixes: 082fbc179c01 ("drm/tests: bridge: Add KUnit tests for bridge chain format selection")
> > Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
>
> Thanks for doing this.
>
> I think I would've also moved the comments with the edid-decode
> results. Matter of taste I guess.
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Yeah, I agree but since it fixes a compilation warning it can be done as
a subsequent patch.
Acked-by: Maxime Ripard <mripard@kernel.org>
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2026-06-10 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 12:13 Nicolas Frattaroli
2026-06-10 12:32 ` Jani Nikula
2026-06-10 13:19 ` Maxime Ripard [this message]
2026-06-10 14:00 ` 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=20260610-quantum-glossy-partridge-136d8b@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=nicolas.frattaroli@collabora.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®