Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Swati Sharma <swati2.sharma@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_content_protection: rename subtests
Date: Tue, 26 Sep 2023 22:12:13 +0530	[thread overview]
Message-ID: <0d03e792-c502-d633-6b31-2c25dddaf8a5@intel.com> (raw)
In-Reply-To: <20230918101150.258055-1-swati2.sharma@intel.com>


On Mon-18-09-2023 03:41 pm, Swati Sharma wrote:
> Use '-' instead of '_' while naming subtests and subtest name
> should use small case.

Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>

> 
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> ---
>   tests/kms_content_protection.c | 12 ++++++------
>   1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index 9378a76c1..ea0c4a0ab 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -491,14 +491,14 @@ test_fini(igt_output_t *output, enum igt_commit_style s)
>   }
>   
>   /**
> - * SUBTEST: LIC
> + * SUBTEST: lic
>    * Description: Test for the integrity of link.
>    * Driver requirement: i915, xe
>    * Functionality: hdcp1.4
>    * Mega feature: HDCP
>    * Test category: functionality test
>    *
> - * SUBTEST: content_type_change
> + * SUBTEST: content-type-change
>    * Description: Test the content type change when the content protection already
>    *              enabled
>    * Driver requirement: i915, xe
> @@ -506,7 +506,7 @@ test_fini(igt_output_t *output, enum igt_commit_style s)
>    * Mega feature: HDCP
>    * Test category: functionality test
>    *
> - * SUBTEST: mei_interface
> + * SUBTEST: mei-interface
>    * Description: Test the teardown and rebuild of the interface between Intel
>    *              and mei hdcp.
>    * Driver requirement: i915, xe
> @@ -802,7 +802,7 @@ static const struct {
>   	  .content_type = HDCP_CONTENT_TYPE_0
>   	},
>   	{ .desc = "Test for the integrity of link.",
> -	  .name = "LIC",
> +	  .name = "lic",
>   	  .cp_tests = CP_LIC,
>   	  .content_type = HDCP_CONTENT_TYPE_0,
>   	},
> @@ -814,12 +814,12 @@ static const struct {
>   	},
>   	{ .desc = "Test the teardown and rebuild of the interface between "
>   		  "Intel and mei hdcp.",
> -	  .name = "mei_interface",
> +	  .name = "mei-interface",
>   	  .cp_tests = CP_MEI_RELOAD,
>   	  .content_type = HDCP_CONTENT_TYPE_1,
>   	},
>   	{ .desc = "Test the content type change when the content protection already enabled",
> -	  .name = "content_type_change",
> +	  .name = "content-type-change",
>   	  .cp_tests = CP_TYPE_CHANGE,
>   	  .content_type = HDCP_CONTENT_TYPE_1,
>   	},

      parent reply	other threads:[~2023-09-26 16:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 10:11 [igt-dev] [PATCH i-g-t] tests/kms_content_protection: rename subtests Swati Sharma
2023-09-18 13:06 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-09-18 13:45 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-09-19 14:26 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-20  8:00 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-09-20  8:22   ` Sharma, Swati2
2023-09-21  6:51 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
2023-09-26 16:42 ` Modem, Bhanuprakash [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=0d03e792-c502-d633-6b31-2c25dddaf8a5@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=swati2.sharma@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