From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, maarten.lankhorst@intel.com
Subject: Re: [Intel-gfx] [PATCH v2 0/4] Fix HFVSDB parsing
Date: Tue, 04 Oct 2022 20:36:22 +0300 [thread overview]
Message-ID: <87lepvsd7t.fsf@intel.com> (raw)
In-Reply-To: <20220916100551.2531750-1-ankit.k.nautiyal@intel.com>
On Fri, 16 Sep 2022, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
> Fix issues in HFVSDB parsing for DSC support.
> Also minor refactoring in Logging.
>
> Split from original patch into a new series.
> https://patchwork.freedesktop.org/patch/495193/
>
> v2: Minor styling fixes.
Thanks for the patches, pushed to drm-misc-next.
BR,
Jani.
>
> Ankit Nautiyal (4):
> drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink
> drm/edid: Split DSC parsing into separate function
> drm/edid: Refactor HFVSDB parsing for DSC1.2
> drm/edid: Avoid multiple log lines for HFVSDB parsing
>
> drivers/gpu/drm/drm_edid.c | 153 +++++++++++++++++++++----------------
> 1 file changed, 87 insertions(+), 66 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2022-10-04 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 10:05 [Intel-gfx] [PATCH v2 0/4] Fix HFVSDB parsing Ankit Nautiyal
2022-09-16 10:05 ` [Intel-gfx] [PATCH v2 1/4] drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink Ankit Nautiyal
2022-09-16 10:05 ` [Intel-gfx] [PATCH v2 2/4] drm/edid: Split DSC parsing into separate function Ankit Nautiyal
2022-09-16 10:05 ` [Intel-gfx] [PATCH v2 3/4] drm/edid: Refactor HFVSDB parsing for DSC1.2 Ankit Nautiyal
2022-09-16 10:05 ` [Intel-gfx] [PATCH v2 4/4] drm/edid: Avoid multiple log lines for HFVSDB parsing Ankit Nautiyal
2022-09-16 11:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fix HFVSDB parsing (rev2) Patchwork
2022-09-16 15:52 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-10-04 17:36 ` 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=87lepvsd7t.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox