From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 00/11] drm/edid: constify EDID parsing, with some fixes
Date: Mon, 28 Mar 2022 16:26:03 +0300 [thread overview]
Message-ID: <87bkxqdx90.fsf@intel.com> (raw)
In-Reply-To: <cover.1648458971.git.jani.nikula@intel.com>
On Mon, 28 Mar 2022, Jani Nikula <jani.nikula@intel.com> wrote:
> v2 of https://patchwork.freedesktop.org/series/101787/ addressing some
> review comments from Ville.
Please ignore this series.
>
> Jani Nikula (11):
> drm/edid: don't modify EDID while parsing
> drm/edid: fix reduced blanking support check
> drm/edid: slightly restructure timing and non-timing descriptor
> structs
> drm/edid: pass a timing pointer to is_display_descriptor()
> drm/edid: use struct detailed_timing member access in is_rb()
> drm/edid: use struct detailed_data_monitor_range member access in gtf2
> functions
> drm/edid: constify struct detailed_timing in lower level parsing
> drm/edid: constify struct detailed_timing in parsing callbacks
> drm/edid: constify struct edid passed to detailed blocks
> drm/edid: constify struct edid passed around in callbacks and closure
> drm/edid: add more general struct edid constness in the interfaces
>
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 6 +-
> drivers/gpu/drm/drm_edid.c | 287 ++++++++++--------
> include/drm/drm_edid.h | 19 +-
> 3 files changed, 174 insertions(+), 138 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2022-03-28 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 9:17 [PATCH v2 00/11] drm/edid: constify EDID parsing, with some fixes Jani Nikula
2022-03-28 9:17 ` [PATCH v2 01/11] drm/edid: don't modify EDID while parsing Jani Nikula
2022-03-28 9:17 ` [PATCH v2 02/11] drm/edid: fix reduced blanking support check Jani Nikula
2022-03-28 16:31 ` Ville Syrjälä
2022-03-28 9:17 ` [PATCH v2 03/11] drm/edid: slightly restructure timing and non-timing descriptor structs Jani Nikula
2022-03-28 9:44 ` Jani Nikula
2022-03-28 11:45 ` [Intel-gfx] " kernel test robot
2022-03-28 13:20 ` Jani Nikula
2022-03-28 12:26 ` kernel test robot
2022-03-28 12:46 ` kernel test robot
2022-03-28 9:17 ` [PATCH v2 04/11] drm/edid: pass a timing pointer to is_display_descriptor() Jani Nikula
2022-03-28 9:17 ` [PATCH v2 05/11] drm/edid: use struct detailed_timing member access in is_rb() Jani Nikula
2022-03-28 9:17 ` [PATCH v2 06/11] drm/edid: use struct detailed_data_monitor_range member access in gtf2 functions Jani Nikula
2022-03-28 9:17 ` [PATCH v2 07/11] drm/edid: constify struct detailed_timing in lower level parsing Jani Nikula
2022-03-28 9:17 ` [PATCH v2 08/11] drm/edid: constify struct detailed_timing in parsing callbacks Jani Nikula
2022-03-28 9:17 ` [PATCH v2 09/11] drm/edid: constify struct edid passed to detailed blocks Jani Nikula
2022-03-28 9:17 ` [PATCH v2 10/11] drm/edid: constify struct edid passed around in callbacks and closure Jani Nikula
2022-03-28 9:17 ` [PATCH v2 11/11] drm/edid: add more general struct edid constness in the interfaces Jani Nikula
2022-03-28 13:26 ` Jani Nikula [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=87bkxqdx90.fsf@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