From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Jani Nikula <jani.nikula@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
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 v3] drm/tests: Move test EDID data to separate .c file
Date: Mon, 15 Jun 2026 13:33:52 +0200 [thread overview]
Message-ID: <F_lbTmMEQRW8DiEaOAuGPw@collabora.com> (raw)
In-Reply-To: <13d51fa273e6577004df793e77d62b76b7a5562e@intel.com>
On Monday, 15 June 2026 11:59:12 Central European Summer Time Jani Nikula wrote:
> On Fri, 12 Jun 2026, Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
> > On Wed, 10 Jun 2026 18:43:43 +0200, Nicolas Frattaroli <nicolas.frattaroli@collabora.com> wrote:
> >> drm/tests: Move test EDID data to separate .c file
> >
> > Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> > Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
>
> Thanks for the patch, review and testing, pushed to drm-misc-next.
>
> BR,
> Jani.
>
On that note, will Intel be picking up the Intel-specific patches from
the color format series as well? Unless they require further changes.
Would be a shame if Intel didn't have this property as well. :(
Kind regards,
Nicolas Frattaroli
prev parent reply other threads:[~2026-06-15 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 16:43 [PATCH v3] drm/tests: Move test EDID data to separate .c file Nicolas Frattaroli
2026-06-10 16:57 ` Jani Nikula
2026-06-11 22:15 ` Luca Ceresoli
2026-06-15 9:59 ` Jani Nikula
2026-06-15 11:33 ` Nicolas Frattaroli [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=F_lbTmMEQRW8DiEaOAuGPw@collabora.com \
--to=nicolas.frattaroli@collabora.com \
--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=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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