From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [CI RESEND 00/10] drm/edid: expand on struct drm_edid usage
Date: Thu, 30 Jun 2022 12:55:29 +0300 [thread overview]
Message-ID: <87bkuapjam.fsf@intel.com> (raw)
In-Reply-To: <cover.1656494768.git.jani.nikula@intel.com>
On Wed, 29 Jun 2022, Jani Nikula <jani.nikula@intel.com> wrote:
> Resend of [1] for CI, also sending without the i915 changes, to be
> merged on top.
And pushed to drm-misc-next. Thanks for the review!
BR,
Jani.
>
> BR,
> Jani.
>
> [1] https://patchwork.freedesktop.org/series/104309/
>
>
> Jani Nikula (10):
> drm/edid: move drm_connector_update_edid_property() to drm_edid.c
> drm/edid: convert drm_connector_update_edid_property() to struct
> drm_edid
> drm/edid: clean up connector update error handling and debug logging
> drm/edid: abstract debugfs override EDID set/reset
> drm/edid: add drm_edid_connector_update()
> drm/probe-helper: add drm_connector_helper_get_modes()
> drm/edid: add drm_edid_raw() to access the raw EDID data
> drm/edid: do invalid block filtering in-place
> drm/edid: add HF-EEODB support to EDID read and allocation
> drm/edid: take HF-EEODB extension count into account
>
> drivers/gpu/drm/drm_connector.c | 74 ------
> drivers/gpu/drm/drm_crtc_internal.h | 5 +-
> drivers/gpu/drm/drm_debugfs.c | 21 +-
> drivers/gpu/drm/drm_edid.c | 376 ++++++++++++++++++++++++----
> drivers/gpu/drm/drm_probe_helper.c | 34 +++
> include/drm/drm_connector.h | 6 +-
> include/drm/drm_edid.h | 3 +
> include/drm/drm_probe_helper.h | 1 +
> 8 files changed, 381 insertions(+), 139 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2022-06-30 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 9:27 [Intel-gfx] [CI RESEND 00/10] drm/edid: expand on struct drm_edid usage Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 01/10] drm/edid: move drm_connector_update_edid_property() to drm_edid.c Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 02/10] drm/edid: convert drm_connector_update_edid_property() to struct drm_edid Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 03/10] drm/edid: clean up connector update error handling and debug logging Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 04/10] drm/edid: abstract debugfs override EDID set/reset Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 05/10] drm/edid: add drm_edid_connector_update() Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 06/10] drm/probe-helper: add drm_connector_helper_get_modes() Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 07/10] drm/edid: add drm_edid_raw() to access the raw EDID data Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 08/10] drm/edid: do invalid block filtering in-place Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 09/10] drm/edid: add HF-EEODB support to EDID read and allocation Jani Nikula
2022-06-29 9:27 ` [Intel-gfx] [CI RESEND 10/10] drm/edid: take HF-EEODB extension count into account Jani Nikula
2022-06-29 11:27 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/edid: expand on struct drm_edid usage (rev8) Patchwork
2022-06-29 11:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-06-30 3:55 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-06-30 9:55 ` 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=87bkuapjam.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