From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, jani.nikula@intel.com
Subject: [PATCH 0/4] drm/edid & drm/i915: vendor and product id logging improvements
Date: Thu, 21 Mar 2024 12:05:08 +0200 [thread overview]
Message-ID: <cover.1711015462.git.jani.nikula@intel.com> (raw)
Jani Nikula (4):
drm/edid: add drm_edid_get_product_id()
drm/edid: add drm_edid_print_product_id()
drm/i915/bios: switch to struct drm_edid and struct
drm_edid_product_id
drm/i915/bios: return drm_edid_product_id from get_lvds_pnp_id()
drivers/gpu/drm/drm_edid.c | 50 +++++++++++++++++++++++
drivers/gpu/drm/i915/display/intel_bios.c | 49 ++++++++++------------
include/drm/drm_edid.h | 28 ++++++++++---
3 files changed, 94 insertions(+), 33 deletions(-)
--
2.39.2
next reply other threads:[~2024-03-21 10:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 10:05 Jani Nikula [this message]
2024-03-21 10:05 ` [PATCH 1/4] drm/edid: add drm_edid_get_product_id() Jani Nikula
2024-04-08 18:10 ` Ville Syrjälä
2024-04-09 7:42 ` Jani Nikula
2024-03-21 10:05 ` [PATCH 2/4] drm/edid: add drm_edid_print_product_id() Jani Nikula
2024-04-08 18:05 ` Ville Syrjälä
2024-04-09 9:41 ` Jani Nikula
2024-03-21 10:05 ` [PATCH 3/4] drm/i915/bios: switch to struct drm_edid and struct drm_edid_product_id Jani Nikula
2024-03-21 10:05 ` [PATCH 4/4] drm/i915/bios: return drm_edid_product_id from get_lvds_pnp_id() Jani Nikula
2024-03-21 11:03 ` ✗ Fi.CI.SPARSE: warning for drm/edid & drm/i915: vendor and product id logging improvements Patchwork
2024-03-21 11:16 ` ✓ Fi.CI.BAT: success " Patchwork
2024-03-22 2:27 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-02 8:49 ` [PATCH 0/4] " Jani Nikula
2024-04-08 12:34 ` Melissa Wen
2024-04-08 13:05 ` Jani Nikula
2024-04-08 13:30 ` Melissa Wen
2024-04-08 13:37 ` 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=cover.1711015462.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 NNTP newsgroup(s).