All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
To: apoorva1.singh@intel.com
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_gpgpu_fill: Add test description
Date: Mon, 7 Dec 2020 09:22:56 +0100	[thread overview]
Message-ID: <20201207082256.GA3532@zkempczy-mobl2> (raw)
In-Reply-To: <20201206121045.263779-1-apoorva1.singh@intel.com>

On Sun, Dec 06, 2020 at 05:40:45PM +0530, apoorva1.singh@intel.com wrote:
> From: Apoorva Singh <apoorva1.singh@intel.com>
> 
> Add description for the test
> 
> Signed-off-by: Apoorva Singh <apoorva1.singh@intel.com>
> Cc: Melkaveri, Arjun <arjun.melkaveri@intel.com>
> ---
>  tests/i915/gem_gpgpu_fill.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/tests/i915/gem_gpgpu_fill.c b/tests/i915/gem_gpgpu_fill.c
> index c605629f..3356892d 100644
> --- a/tests/i915/gem_gpgpu_fill.c
> +++ b/tests/i915/gem_gpgpu_fill.c
> @@ -47,6 +47,8 @@
>  #include "igt.h"
>  #include "intel_bufops.h"
>  
> +IGT_TEST_DESCRIPTION("Test for the gpgpu fill function - a very simple workload for the GPGPU pipeline");
> +

Maybe "Verify surface is filled correctly using GPGPU pipeline"?

--
Zbigniew 


>  #define WIDTH 64
>  #define HEIGHT 64
>  #define STRIDE (WIDTH)
> -- 
> 2.25.1
> 
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      parent reply	other threads:[~2020-12-07  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 12:10 [igt-dev] [PATCH i-g-t] i915/gem_gpgpu_fill: Add test description apoorva1.singh
2020-12-06 13:06 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-12-06 17:33 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-12-07  8:22 ` Zbigniew Kempczyński [this message]

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=20201207082256.GA3532@zkempczy-mobl2 \
    --to=zbigniew.kempczynski@intel.com \
    --cc=apoorva1.singh@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 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.