From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: jari.tahvanainen@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915/kms_fb_coherency: add mega-feature and functionality
Date: Fri, 23 Jun 2023 08:51:36 +0530 [thread overview]
Message-ID: <8b8f4217-e95f-f1db-25e2-58462d07f5a9@intel.com> (raw)
In-Reply-To: <20230622123014.4184296-1-mauro.chehab@linux.intel.com>
Hi Mauro,
On Thu-22-06-2023 06:00 pm, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab <mchehab@kernel.org>
>
> This test is currently missing mega-feature and functionality.
> Add them.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
> tests/i915/kms_fb_coherency.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/i915/kms_fb_coherency.c b/tests/i915/kms_fb_coherency.c
> index b530bf5dcd70..ba0ea7068fdf 100644
> --- a/tests/i915/kms_fb_coherency.c
> +++ b/tests/i915/kms_fb_coherency.c
> @@ -6,6 +6,8 @@
> /**
> * TEST: kms_fb_coherency
> * Description: Exercise coherency of future scanout buffer objects
> + * Mega feature: General Display Features
> + * Functionality: crc
For display tests, "Mega feature" & "Functionality" should be at SUBTEST
level.
Also, Functionality must be gtt or kms_gem_interop, since this test is
trying to validate different mappings.
- Bhanu
> */
>
> #include <errno.h>
next prev parent reply other threads:[~2023-06-23 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 12:30 [igt-dev] [PATCH i-g-t] tests/i915/kms_fb_coherency: add mega-feature and functionality Mauro Carvalho Chehab
2023-06-22 12:43 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-06-22 13:15 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-22 23:51 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-06-23 3:21 ` Modem, Bhanuprakash [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-23 10:23 [igt-dev] [PATCH i-g-t] " Mauro Carvalho Chehab
2023-06-24 5:46 ` Modem, Bhanuprakash
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=8b8f4217-e95f-f1db-25e2-58462d07f5a9@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=mauro.chehab@linux.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