From: Swati Sharma <swati2.sharma@intel.com>
To: "Hogander, Jouni" <jouni.hogander@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v2 0/6] Enable VDSC output formats validation
Date: Fri, 3 Feb 2023 16:23:33 +0530 [thread overview]
Message-ID: <fc168b9a-fe35-d12f-0660-321961ed1f02@intel.com> (raw)
In-Reply-To: <bb717e27b3fdcea17ca83e9b23b4809f41275516.camel@intel.com>
Thanks for the review. Pushed 4/6 patches.
On 02-Feb-23 4:22 PM, Hogander, Jouni wrote:
> On Thu, 2023-02-02 at 12:51 +0530, Swati Sharma wrote:
>> This series is split from
>> https://patchwork.freedesktop.org/series/111342/
>>
>> Initial dsc lib related changes got merged. Received review
>> comments on driver debugfs YCBCR420 changes, to make debugfs
>> entry generic so that all supported output formats can be
>> validated.
>>
>> In this series, review comments from above PW are addressed.
>> Along, with that changes are done to make test generic to
>> validate all supported dsc formats.
>
> For the whole set:
>
> Reviewed-by: Jouni Högander <jouni.hogander@intel.com>
>
>>
>> Swati Sharma (6):
>> lib/dsc: Fix return value
>> tests/i915/kms_dsc: Add plane_format as struct data_t member
>> tests/i915/kms_dsc: Remove pointless struct
>> tests/i915/kms_dsc: Make bpc_list static
>> lib/dsc: Add helpers for VDSC output format debugfs entry
>> tests/i915/kms_dsc: Enable validation for VDSC output formats
>>
>> lib/igt_dsc.c | 56 +++++++++++++++-
>> lib/igt_dsc.h | 5 ++
>> lib/igt_kms.c | 18 +++++
>> lib/igt_kms.h | 7 ++
>> tests/i915/kms_dsc.c | 128 ++++++++++++++++++++++++++--------
>> --
>> tests/i915/kms_dsc_helper.c | 40 ++++++++++-
>> tests/i915/kms_dsc_helper.h | 4 ++
>> 7 files changed, 218 insertions(+), 40 deletions(-)
>>
>
--
~Swati Sharma
next prev parent reply other threads:[~2023-02-03 10:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 7:21 [igt-dev] [PATCH i-g-t v2 0/6] Enable VDSC output formats validation Swati Sharma
2023-02-02 7:21 ` [igt-dev] [PATCH i-g-t v2 1/6] lib/dsc: Fix return value Swati Sharma
2023-02-02 7:21 ` [igt-dev] [PATCH i-g-t v2 2/6] tests/i915/kms_dsc: Add plane_format as struct data_t member Swati Sharma
2023-02-02 7:21 ` [igt-dev] [PATCH i-g-t v2 3/6] tests/i915/kms_dsc: Remove pointless struct Swati Sharma
2023-02-03 12:29 ` Kamil Konieczny
2023-02-03 13:26 ` Swati Sharma
2023-02-02 7:21 ` [igt-dev] [PATCH i-g-t v2 4/6] tests/i915/kms_dsc: Make bpc_list static Swati Sharma
2023-02-02 7:21 ` [igt-dev] [PATCH i-g-t v2 5/6] lib/dsc: Add helpers for VDSC output format debugfs entry Swati Sharma
2023-02-03 12:39 ` Kamil Konieczny
2023-02-03 13:28 ` Swati Sharma
2023-02-02 7:21 ` [igt-dev] [PATCH i-g-t v2 6/6] tests/i915/kms_dsc: Enable validation for VDSC output formats Swati Sharma
2023-02-02 7:48 ` [igt-dev] ✓ Fi.CI.BAT: success for Enable VDSC output formats validation (rev2) Patchwork
2023-02-02 10:52 ` [igt-dev] [PATCH i-g-t v2 0/6] Enable VDSC output formats validation Hogander, Jouni
2023-02-03 10:53 ` Swati Sharma [this message]
2023-02-02 16:00 ` [igt-dev] ✓ Fi.CI.IGT: success for Enable VDSC output formats validation (rev2) Patchwork
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=fc168b9a-fe35-d12f-0660-321961ed1f02@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jouni.hogander@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