Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Modem@linux.intel.com
Subject: [igt-dev] [PATCH i-g-t] tests/i915/kms_fb_coherency: add mega-feature and functionality
Date: Fri, 23 Jun 2023 12:23:31 +0200	[thread overview]
Message-ID: <20230623102331.40250-1-mauro.chehab@linux.intel.com> (raw)

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..edb5ba460fbf 100644
--- a/tests/i915/kms_fb_coherency.c
+++ b/tests/i915/kms_fb_coherency.c
@@ -243,6 +243,8 @@ igt_main
 	 * Description: Use display controller CRC hardware to validate (non)coherency
 	 *		of memset operations on future scanout buffer objects
 	 *		mmapped with different mmap methods and different caching modes.
+	 * Mega feature: General Display Features
+	 * Functionality: gtt
 	 */
 	igt_subtest_with_dynamic("memset-crc") {
 		if (gem_has_mappable_ggtt(data.drm_fd)) {
-- 
2.40.1

             reply	other threads:[~2023-06-23 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 10:23 Mauro Carvalho Chehab [this message]
2023-06-23 11:10 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/kms_fb_coherency: add mega-feature and functionality (rev2) Patchwork
2023-06-23 16:21 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-06-24  5:46 ` [igt-dev] [PATCH i-g-t] tests/i915/kms_fb_coherency: add mega-feature and functionality Modem, Bhanuprakash
  -- strict thread matches above, loose matches on Subject: below --
2023-06-22 12:30 Mauro Carvalho Chehab
2023-06-23  3:21 ` 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=20230623102331.40250-1-mauro.chehab@linux.intel.com \
    --to=mauro.chehab@linux.intel.com \
    --cc=Modem@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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