Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] tests/drm_import_export: Added test description for test case
Date: Wed, 23 Mar 2022 14:26:05 +0100	[thread overview]
Message-ID: <Yjsf7dyABW47Ga50@kamilkon-DESK1> (raw)
In-Reply-To: <20220321140950.268112-2-priyanka.dandamudi@intel.com>

Hi Priyanka,

Dnia 2022-03-21 at 19:39:49 +0530, priyanka.dandamudi@intel.com napisał(a):
> From: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
> 
> Added test description to all the test and subtests.
> 
> Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Cc: Melkaveri Arjun <arjun.melkaveri@intel.com>
> ---
>  tests/drm_import_export.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/tests/drm_import_export.c b/tests/drm_import_export.c
> index 65cac60d..e21ac8ae 100644
> --- a/tests/drm_import_export.c
> +++ b/tests/drm_import_export.c
> @@ -43,6 +43,7 @@
>  #include "i915/gem.h"
>  
>  #define DURATION 10
> +IGT_TEST_DESCRIPTION("Basic check to verify the behaviour of libdrm bo for prime/flink");
>  
>  int fd;
>  drm_intel_bufmgr *bufmgr;
> @@ -250,16 +251,22 @@ igt_main {
>  		drm_intel_bufmgr_gem_enable_reuse(bufmgr);
>  	}
>  
> +	igt_describe("Verify whether the behaviour of libdrm"
> +                     " is consistent for flink or not.");
-- ^^
Please use tabs then few spaces before string.

>  	igt_subtest("import-close-race-flink") {
>  		use_flink = true;
>  		test_import_close_race();
>  	}
>  
> + 	igt_describe("Verify whether the behaviour of libdrm"
-- ^
Remove space before tab.

> +                     " is consistent for prime or not.");

Same as above, change to tabs then few spaces.

>  	igt_subtest("import-close-race-prime") {
>  		use_flink = false;
>  		test_import_close_race();
>  	}
>  
> +	igt_describe("Multithreaded test to validate the (lack of) locking in the flink"
----------------------------------------------------------------------------- ^
You already splitted this string, so split it here to keep under
80 columns.

> +    		     "code in libdrm-intel.");
-- ^
Remove spaces before tabs.
You already used "libdrm" above, so s/libdrm-intel/libdrm/
Please also put space between words, here it get "flinkcode"

>  	igt_subtest("flink") {
>  		use_flink = true;
>  
> @@ -274,6 +281,8 @@ igt_main {
>  		pthread_join(test_thread_id4, NULL);
>  	}
>  
> +	igt_describe("Multithreaded test to validate the (lack of) locking in the prime"

Split string to keep it under 80 columns.

> +                     "code in libdrm-intel.");
-- ^
Change spaces to tabs, then few spaces.
s/libdrm-intel/libdrm/

Please use --describe to see for missed spaces between words.

>  	igt_subtest("prime") {
>  		use_flink = false;
>  
> -- 
> 2.25.1
> 
Regards,
Kamil

  reply	other threads:[~2022-03-23 13:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 14:09 [igt-dev] [PATCH i-g-t 0/2] HAX add description to drm_import_export priyanka.dandamudi
2022-03-21 14:09 ` [igt-dev] [PATCH i-g-t 1/2] tests/drm_import_export: Added test description for test case priyanka.dandamudi
2022-03-23 13:26   ` Kamil Konieczny [this message]
2022-03-21 14:09 ` [igt-dev] [PATCH i-g-t 2/2] HAX: don't do full run priyanka.dandamudi
2022-03-21 15:14 ` [igt-dev] ✗ Fi.CI.BAT: failure for HAX add description to drm_import_export Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2022-03-24 10:27 [igt-dev] [PATCH i-g-t 0/2] " priyanka.dandamudi
2022-03-24 10:27 ` [igt-dev] [PATCH i-g-t 1/2] tests/drm_import_export: Added test description for test case priyanka.dandamudi
2022-04-28 13:59   ` Kamil Konieczny

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=Yjsf7dyABW47Ga50@kamilkon-DESK1 \
    --to=kamil.konieczny@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