From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Lankhorst, Maarten" <maarten.lankhorst@intel.com>
Subject: Re: [Intel-gfx] [PATCH 0/4] Fix HFVSDB parsing
Date: Fri, 12 Aug 2022 10:28:15 +0530 [thread overview]
Message-ID: <82e10ed3-efc0-e1ae-3c12-d6ff6fc691d2@intel.com> (raw)
In-Reply-To: <DM6PR11MB31770EF1BA81D104ACE92D85BA679@DM6PR11MB3177.namprd11.prod.outlook.com>
Hi Arun,
You are right, I missed to add dri-devel here :(
I had send this series to dri-devel again.
Thanks & Regards,
Ankit
On 8/12/2022 9:01 AM, Murthy, Arun R wrote:
> I think this series will have to be posted to dri-devel as well.
>
> Thanks and Regards,
> Arun R Murthy
> -------------------
>
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Ankit
>> Nautiyal
>> Sent: Thursday, August 11, 2022 10:30 AM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Lankhorst, Maarten <maarten.lankhorst@intel.com>
>> Subject: [Intel-gfx] [PATCH 0/4] Fix HFVSDB parsing
>>
>> 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/
>>
>> 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(-)
>>
>> --
>> 2.25.1
prev parent reply other threads:[~2022-08-12 4:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 4:59 [Intel-gfx] [PATCH 0/4] Fix HFVSDB parsing Ankit Nautiyal
2022-08-11 4:59 ` [Intel-gfx] [PATCH 1/4] drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink Ankit Nautiyal
2022-08-11 4:59 ` [Intel-gfx] [PATCH 2/4] drm/edid: Split DSC parsing into separate function Ankit Nautiyal
2022-08-11 4:59 ` [Intel-gfx] [PATCH 3/4] drm/edid: Refactor HFVSDB parsing for DSC1.2 Ankit Nautiyal
2022-08-11 4:59 ` [Intel-gfx] [PATCH 4/4] drm/edid: Avoid multiple log lines for HFVSDB parsing Ankit Nautiyal
2022-08-11 7:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fix " Patchwork
2022-08-11 19:37 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-08-12 3:31 ` [Intel-gfx] [PATCH 0/4] " Murthy, Arun R
2022-08-12 4:58 ` Nautiyal, Ankit K [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=82e10ed3-efc0-e1ae-3c12-d6ff6fc691d2@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--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