From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Ranjeet Kumar <ranjeet1.kumar@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] i915/gem_set_tiling_vs_pwrite: Added description for test case
Date: Wed, 27 Apr 2022 17:22:29 +0200 [thread overview]
Message-ID: <YmlftRF0b9r+4etf@kamilkon-DESK1> (raw)
In-Reply-To: <20220426041228.516686-2-priyanka.dandamudi@intel.com>
Hi Priyanka,
please check with ./gem_set_tiling_vs_pwrite --describe if there
is missing description and where to add it. Do this check again
after you add description to see if anything is missing. In this
case this is simple test without any subtests, so only global
description is needed and it is already present at begin of file.
Sorry but this patch cannot be merged.
Regards,
Kamil
On 2022-04-26 at 09:42:27 +0530, priyanka.dandamudi@intel.com wrote:
> From: ranjeet kumar <ranjeet1.kumar@intel.com>
>
> Added test description for subtest.
>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Signed-off-by: ranjeet kumar <ranjeet1.kumar@intel.com>
> Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
> ---
> tests/i915/gem_set_tiling_vs_pwrite.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/tests/i915/gem_set_tiling_vs_pwrite.c b/tests/i915/gem_set_tiling_vs_pwrite.c
> index 6bec7f27..7e96ad96 100644
> --- a/tests/i915/gem_set_tiling_vs_pwrite.c
> +++ b/tests/i915/gem_set_tiling_vs_pwrite.c
> @@ -74,7 +74,7 @@ igt_simple_main
> *ptr = 0xdeadbeef;
> }
>
> - igt_info("testing pwrite on tiled buffer\n");
> + igt_describe("Set tiling stride and domain and check pwrite coherency on tiled buffer.");
> gem_write(fd, handle, 0, data, OBJECT_SIZE);
> memset(data, 0, OBJECT_SIZE);
> gem_read(fd, handle, 0, data, OBJECT_SIZE);
> @@ -90,7 +90,8 @@ igt_simple_main
>
> gem_set_tiling(fd, handle, I915_TILING_NONE, 0);
>
> - igt_info("testing pwrite on untiled, but still fenced buffer\n");
> + igt_describe("set tiling stride as none and domain and check pwrite coherency on"
> + " still fenced buffer.");
> gem_write(fd, handle, 0, data, OBJECT_SIZE);
> memset(data, 0, OBJECT_SIZE);
> gem_read(fd, handle, 0, data, OBJECT_SIZE);
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-04-27 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 4:12 [igt-dev] [PATCH i-g-t 0/2] HAX add description to gem_set_tiling_vs_pwrite priyanka.dandamudi
2022-04-26 4:12 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_set_tiling_vs_pwrite: Added description for test case priyanka.dandamudi
2022-04-27 15:22 ` Kamil Konieczny [this message]
2022-04-26 4:12 ` [igt-dev] [PATCH i-g-t 2/2] HAX: don't do full run priyanka.dandamudi
2022-04-26 4:41 ` [igt-dev] ✗ Fi.CI.BAT: failure for HAX add description to gem_set_tiling_vs_pwrite 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=YmlftRF0b9r+4etf@kamilkon-DESK1 \
--to=kamil.konieczny@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ranjeet1.kumar@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