All of lore.kernel.org
 help / color / mirror / Atom feed
From: sai.gowtham.ch@intel.com
To: igt-dev@lists.freedesktop.org, kamil.konieczny@linux.intel.com,
	sai.gowtham.ch@intel.com
Subject: [igt-dev] [PATCH i-g-t 1/2] i915/gem_tiled_pread_basic: Add test description
Date: Thu, 16 Jun 2022 12:01:22 +0530	[thread overview]
Message-ID: <20220616063123.11029-2-sai.gowtham.ch@intel.com> (raw)
In-Reply-To: <20220616063123.11029-1-sai.gowtham.ch@intel.com>

From: Sai Gowtham Ch <sai.gowtham.ch@intel.com>

Add test description to the test.

Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Signed-off-by: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
---
 tests/i915/gem_tiled_pread_basic.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/i915/gem_tiled_pread_basic.c b/tests/i915/gem_tiled_pread_basic.c
index 2b4cec6e..4f3ffb20 100644
--- a/tests/i915/gem_tiled_pread_basic.c
+++ b/tests/i915/gem_tiled_pread_basic.c
@@ -50,7 +50,9 @@
 #include "i915/gem_create.h"
 
 IGT_TEST_DESCRIPTION("Test pread behavior on tiled objects with respect to the"
-		     " reported swizzling value.");
+		     " reported swizzling value. The goal is to exercise the"
+		     " slow_bit17_copy path for reading on bit17 machines,"
+		     " but will also be useful for catching swizzling value bugs on");
 
 #define WIDTH 512
 #define HEIGHT 512
-- 
2.35.1

  reply	other threads:[~2022-06-16  6:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  6:31 [igt-dev] [PATCH i-g-t 0/2] HAX add description to gem_tiled_pread_basic sai.gowtham.ch
2022-06-16  6:31 ` sai.gowtham.ch [this message]
2022-06-21 16:18   ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_tiled_pread_basic: Add test description Kamil Konieczny
2022-06-16  6:31 ` [igt-dev] [PATCH i-g-t 2/2] HAX: don't do full run sai.gowtham.ch
2022-06-16  7:16 ` [igt-dev] ✗ Fi.CI.BAT: failure for HAX add description to gem_tiled_pread_basic 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=20220616063123.11029-2-sai.gowtham.ch@intel.com \
    --to=sai.gowtham.ch@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.