All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode
Date: Tue, 5 Oct 2021 15:39:16 +0530	[thread overview]
Message-ID: <d79c7839-b26e-2c44-c6bf-69be050be2c0@intel.com> (raw)
In-Reply-To: <20210916153515.21369-1-ville.syrjala@linux.intel.com>

On 9/16/2021 9:05 PM, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Let's add some more tests for invalid modes. To that end rename
> the current kms_invalid_dotclock to kms_invalid_mode so we a

Hi,

Typo? so we a -> so we (have) a?

With this updated, looks good to me.

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

> place where to put these.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>   tests/i915/{kms_invalid_dotclock.c => kms_invalid_mode.c} | 2 +-
>   tests/meson.build                                         | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>   rename tests/i915/{kms_invalid_dotclock.c => kms_invalid_mode.c} (99%)
>
> diff --git a/tests/i915/kms_invalid_dotclock.c b/tests/i915/kms_invalid_mode.c
> similarity index 99%
> rename from tests/i915/kms_invalid_dotclock.c
> rename to tests/i915/kms_invalid_mode.c
> index 95136d366dd7..dc30e6bb5444 100644
> --- a/tests/i915/kms_invalid_dotclock.c
> +++ b/tests/i915/kms_invalid_mode.c
> @@ -25,7 +25,7 @@
>   #include "igt.h"
>   #include <stdbool.h>
>   
> -IGT_TEST_DESCRIPTION("Make sure all modesets are rejected when the requested dotclock is too high");
> +IGT_TEST_DESCRIPTION("Make sure all modesets are rejected when the requested mode is invalid");
>   
>   typedef struct {
>   	int drm_fd;
> diff --git a/tests/meson.build b/tests/meson.build
> index 8ad52596a491..3e3090e5d8b4 100644
> --- a/tests/meson.build
> +++ b/tests/meson.build
> @@ -228,7 +228,7 @@ i915_progs = [
>   	'kms_flip_scaled_crc',
>   	'kms_flip_tiling',
>   	'kms_frontbuffer_tracking',
> -	'kms_invalid_dotclock',
> +	'kms_invalid_mode',
>   	'kms_legacy_colorkey',
>   	'kms_mmap_write_crc',
>   	'kms_pipe_b_c_ivb',


  parent reply	other threads:[~2021-10-05 10:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 15:35 [igt-dev] [PATCH i-g-t 1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Ville Syrjala
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 2/6] tests/kms_invalid_mode: Convert the max dotclock test into a subtest Ville Syrjala
2021-10-05 10:13   ` Karthik B S
2021-10-05 10:33     ` Petri Latvala
2021-10-05 10:38       ` Ville Syrjälä
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 3/6] tests/kms_invalid_mode: Move bigjoiner handling into the proper place Ville Syrjala
2021-10-05 10:15   ` Karthik B S
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 4/6] tests/kms_invalid_mode: Test various bogus timings Ville Syrjala
2021-10-05 10:22   ` Karthik B S
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 5/6] tests/kms_invalid_mode: Test clock==(U)INT_MAX Ville Syrjala
2021-10-05 10:24   ` Karthik B S
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 6/6] tests/kms_invalid_mode: Allow the test on !i915 Ville Syrjala
2021-10-05 10:27   ` Karthik B S
2021-09-16 19:05 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Patchwork
2021-09-22 17:16 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode (rev2) Patchwork
2021-09-22 19:09 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-10-04 12:30 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode (rev3) Patchwork
2021-10-04 14:54 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-10-05 10:09 ` Karthik B S [this message]
2021-10-05 11:12   ` [igt-dev] [PATCH i-g-t 1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Ville Syrjälä

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=d79c7839-b26e-2c44-c6bf-69be050be2c0@intel.com \
    --to=karthik.b.s@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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 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.