From: Maxime Ripard <mripard@kernel.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>
Cc: Dmitry Baryshkov <lumag@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Maxime Ripard <mripard@kernel.org>
Subject: [PATCH 0/3] drm/tests: edid: Improve our kunit EDIDs
Date: Wed, 25 Jun 2025 17:14:34 +0200 [thread overview]
Message-ID: <20250625-drm-update-edid-v1-0-2d963743ab9e@kernel.org> (raw)
Hi,
Here's a series fixing a few issues I found looking into our kunit EDIDs
some more.
Let me know what you think,
Maxime
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
Maxime Ripard (3):
drm/tests: edid: Fix monitor range limits
drm/tests: edid: Update CTA-861 HDMI Vendor Specific Data Block
drm/tests: edid: Add edid-decode --check output
drivers/gpu/drm/tests/drm_kunit_edid.h | 142 ++++++++++++++++++++++-----------
1 file changed, 94 insertions(+), 48 deletions(-)
---
base-commit: e04c78d86a9699d136910cfc0bdcf01087e3267e
change-id: 20250625-drm-update-edid-590c388be7cb
Best regards,
--
Maxime Ripard <mripard@kernel.org>
next reply other threads:[~2025-06-25 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 15:14 Maxime Ripard [this message]
2025-06-25 15:14 ` [PATCH 1/3] drm/tests: edid: Fix monitor range limits Maxime Ripard
2025-07-10 12:09 ` Javier Martinez Canillas
2025-06-25 15:14 ` [PATCH 2/3] drm/tests: edid: Update CTA-861 HDMI Vendor Specific Data Block Maxime Ripard
2025-07-10 12:13 ` Javier Martinez Canillas
2025-07-14 11:02 ` Thomas Zimmermann
2025-07-16 15:06 ` Maxime Ripard
2025-07-16 15:34 ` Thomas Zimmermann
2025-07-28 8:37 ` Jani Nikula
2025-06-25 15:14 ` [PATCH 3/3] drm/tests: edid: Add edid-decode --check output Maxime Ripard
2025-07-10 12:16 ` Javier Martinez Canillas
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=20250625-drm-update-edid-v1-0-2d963743ab9e@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.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;
as well as URLs for NNTP newsgroup(s).