Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: Swati Sharma <swati2.sharma@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_sequence: remove redundant test doc
Date: Wed, 27 Sep 2023 08:52:51 +0530	[thread overview]
Message-ID: <1fdbd286-6682-1950-dc90-2d2b18fc5ed0@intel.com> (raw)
In-Reply-To: <20230918104130.259103-1-swati2.sharma@intel.com>


On 9/18/2023 4:11 PM, Swati Sharma wrote:
> We already have IGT_TEST_DESCRIPTION and even testplan
> documentation, no need to redundant documentation.

'to' -> 'for'

With this update,

Reviewed-by: Karthik B S <karthik.b.s@intel.com>

>
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> ---
>   tests/kms_sequence.c | 5 -----
>   1 file changed, 5 deletions(-)
>
> diff --git a/tests/kms_sequence.c b/tests/kms_sequence.c
> index 9476203e9..c6d6dea00 100644
> --- a/tests/kms_sequence.c
> +++ b/tests/kms_sequence.c
> @@ -22,11 +22,6 @@
>    * IN THE SOFTWARE.
>    */
>   
> -/** @file kms_sequence.c
> - *
> - * This is a test of drmCrtcGetSequence and drmCrtcQueueSequence
> - */
> -
>   /**
>    * TEST: kms sequence
>    * Category: Display

      parent reply	other threads:[~2023-09-27  3:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 10:41 [igt-dev] [PATCH i-g-t] tests/kms_sequence: remove redundant test doc Swati Sharma
2023-09-18 15:42 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-09-18 16:03 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-09-18 16:10 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-09-19 18:06 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-21  6:15 ` Patchwork
2023-09-21  6:45 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2023-09-21  7:02 ` Patchwork
2023-09-27  3:22 ` Karthik B S [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=1fdbd286-6682-1950-dc90-2d2b18fc5ed0@intel.com \
    --to=karthik.b.s@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