From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 00/12] drm/edid: cleanup and refactoring around validity checks
Date: Fri, 1 Apr 2022 17:11:04 +0300 [thread overview]
Message-ID: <YkcH+OO+lVBejjn4@intel.com> (raw)
In-Reply-To: <877d8989om.fsf@intel.com>
On Fri, Apr 01, 2022 at 11:55:21AM +0300, Jani Nikula wrote:
> On Thu, 31 Mar 2022, Jani Nikula <jani.nikula@intel.com> wrote:
> > v2 of https://patchwork.freedesktop.org/series/101931/
> >
> > Rebased, review comments addressed.
>
> Ville, care to double check patches 1 & 7 please?
Looks fine by me
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Thanks,
> Jani.
>
>
> >
> > BR,
> > Jani.
> >
> >
> >
> > Jani Nikula (12):
> > drm/edid: use struct edid * in drm_do_get_edid()
> > drm/edid: clean up EDID block checksum functions
> > drm/edid: add edid_block_tag() helper to get the EDID extension tag
> > drm/edid: make drm_edid_header_is_valid() accept void pointer
> > drm/edid: clean up edid_is_zero()
> > drm/edid: split out edid_header_fix()
> > drm/edid: split drm_edid_block_valid() to check and act parts
> > drm/edid: use a better variable name for EDID block read retries
> > drm/edid: simplify block check when filtering invalid blocks
> > drm/edid: split out invalid block filtering to a separate function
> > drm/edid: track invalid blocks in drm_do_get_edid()
> > drm/edid: reduce magic when updating the EDID block checksum
> >
> > drivers/gpu/drm/drm_edid.c | 295 +++++++++++++++++++++----------------
> > include/drm/drm_edid.h | 2 +-
> > 2 files changed, 173 insertions(+), 124 deletions(-)
>
> --
> Jani Nikula, Intel Open Source Graphics Center
--
Ville Syrjälä
Intel
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 00/12] drm/edid: cleanup and refactoring around validity checks
Date: Fri, 1 Apr 2022 17:11:04 +0300 [thread overview]
Message-ID: <YkcH+OO+lVBejjn4@intel.com> (raw)
In-Reply-To: <877d8989om.fsf@intel.com>
On Fri, Apr 01, 2022 at 11:55:21AM +0300, Jani Nikula wrote:
> On Thu, 31 Mar 2022, Jani Nikula <jani.nikula@intel.com> wrote:
> > v2 of https://patchwork.freedesktop.org/series/101931/
> >
> > Rebased, review comments addressed.
>
> Ville, care to double check patches 1 & 7 please?
Looks fine by me
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Thanks,
> Jani.
>
>
> >
> > BR,
> > Jani.
> >
> >
> >
> > Jani Nikula (12):
> > drm/edid: use struct edid * in drm_do_get_edid()
> > drm/edid: clean up EDID block checksum functions
> > drm/edid: add edid_block_tag() helper to get the EDID extension tag
> > drm/edid: make drm_edid_header_is_valid() accept void pointer
> > drm/edid: clean up edid_is_zero()
> > drm/edid: split out edid_header_fix()
> > drm/edid: split drm_edid_block_valid() to check and act parts
> > drm/edid: use a better variable name for EDID block read retries
> > drm/edid: simplify block check when filtering invalid blocks
> > drm/edid: split out invalid block filtering to a separate function
> > drm/edid: track invalid blocks in drm_do_get_edid()
> > drm/edid: reduce magic when updating the EDID block checksum
> >
> > drivers/gpu/drm/drm_edid.c | 295 +++++++++++++++++++++----------------
> > include/drm/drm_edid.h | 2 +-
> > 2 files changed, 173 insertions(+), 124 deletions(-)
>
> --
> Jani Nikula, Intel Open Source Graphics Center
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-04-01 14:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 18:44 [Intel-gfx] [PATCH v2 00/12] drm/edid: cleanup and refactoring around validity checks Jani Nikula
2022-03-31 18:44 ` Jani Nikula
2022-03-31 18:44 ` [Intel-gfx] [PATCH v2 01/12] drm/edid: use struct edid * in drm_do_get_edid() Jani Nikula
2022-03-31 18:44 ` Jani Nikula
2022-03-31 18:44 ` [Intel-gfx] [PATCH v2 02/12] drm/edid: clean up EDID block checksum functions Jani Nikula
2022-03-31 18:44 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 03/12] drm/edid: add edid_block_tag() helper to get the EDID extension tag Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 04/12] drm/edid: make drm_edid_header_is_valid() accept void pointer Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 05/12] drm/edid: clean up edid_is_zero() Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 06/12] drm/edid: split out edid_header_fix() Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 07/12] drm/edid: split drm_edid_block_valid() to check and act parts Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 08/12] drm/edid: use a better variable name for EDID block read retries Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 09/12] drm/edid: simplify block check when filtering invalid blocks Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 10/12] drm/edid: split out invalid block filtering to a separate function Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 11/12] drm/edid: track invalid blocks in drm_do_get_edid() Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 18:45 ` [Intel-gfx] [PATCH v2 12/12] drm/edid: reduce magic when updating the EDID block checksum Jani Nikula
2022-03-31 18:45 ` Jani Nikula
2022-03-31 21:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/edid: cleanup and refactoring around validity checks (rev2) Patchwork
2022-03-31 21:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-01 3:20 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-04-01 8:55 ` [Intel-gfx] [PATCH v2 00/12] drm/edid: cleanup and refactoring around validity checks Jani Nikula
2022-04-01 8:55 ` Jani Nikula
2022-04-01 14:11 ` Ville Syrjälä [this message]
2022-04-01 14:11 ` Ville Syrjälä
2022-04-01 16:18 ` [Intel-gfx] " Jani Nikula
2022-04-01 16:18 ` 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=YkcH+OO+lVBejjn4@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.