public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mika Kahola <mika.kahola@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v2 8/8] tests: Rename kms_pipe_color to kms_color
Date: Fri, 29 Sep 2017 13:00:04 +0300	[thread overview]
Message-ID: <1506679204.3274.18.camel@intel.com> (raw)
In-Reply-To: <20170927181635.21170-9-maarten.lankhorst@linux.intel.com>

Name change is ok to help the work in the future.

On Wed, 2017-09-27 at 20:16 +0200, Maarten Lankhorst wrote:
> Rename kms_pipe_color to kms_color, and rename the invalid tests to
> pipe-invalid.
> To prepare for adding support for plane color management.
> 
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Mika Kahola <mika.kahola@intel.com>

> ---
>  tests/Makefile.sources                  | 2 +-
>  tests/{kms_pipe_color.c => kms_color.c} | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
>  rename tests/{kms_pipe_color.c => kms_color.c} (99%)
> 
> diff --git a/tests/Makefile.sources b/tests/Makefile.sources
> index 0adc28a014d2..c4d320ebc61b 100644
> --- a/tests/Makefile.sources
> +++ b/tests/Makefile.sources
> @@ -177,6 +177,7 @@ TESTS_progs = \
>  	kms_busy \
>  	kms_ccs \
>  	kms_chv_cursor_fail \
> +	kms_color \
>  	kms_concurrent \
>  	kms_crtc_background_color \
>  	kms_cursor_crc \
> @@ -197,7 +198,6 @@ TESTS_progs = \
>  	kms_mmio_vs_cs_flip \
>  	kms_panel_fitting \
>  	kms_pipe_b_c_ivb \
> -	kms_pipe_color \
>  	kms_pipe_crc_basic \
>  	kms_plane \
>  	kms_plane_lowres \
> diff --git a/tests/kms_pipe_color.c b/tests/kms_color.c
> similarity index 99%
> rename from tests/kms_pipe_color.c
> rename to tests/kms_color.c
> index ccfc08e6be15..060a60152808 100644
> --- a/tests/kms_pipe_color.c
> +++ b/tests/kms_color.c
> @@ -1205,10 +1205,10 @@ igt_main
>  		igt_subtest_group
>  			run_tests_for_pipe(&data, pipe);
>  
> -	igt_subtest_f("invalid-lut-sizes")
> +	igt_subtest_f("pipe-invalid-lut-sizes")
>  		invalid_lut_sizes(&data);
>  
> -	igt_subtest_f("invalid-ctm-matrix-sizes")
> +	igt_subtest_f("pipe-invalid-ctm-matrix-sizes")
>  		invalid_ctm_matrix_sizes(&data);
>  
>  	igt_fixture {
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-09-29  9:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 18:16 [PATCH i-g-t v2 0/8] lib/igt_kms: Convert properties to be more atomic-like Maarten Lankhorst
2017-09-27 18:16 ` [PATCH i-g-t v2 1/8] tests: Stop looking at plane private members Maarten Lankhorst
2017-09-27 18:16 ` [PATCH i-g-t v2 2/8] lib/igt_kms: Change output->pending_crtc_idx_mask to output->pending_pipe Maarten Lankhorst
2017-09-27 18:16 ` [PATCH i-g-t v2 3/8] lib/igt_kms: Commit primary plane when a modeset is forced on a pipe Maarten Lankhorst
2017-09-27 18:16 ` [PATCH i-g-t v2 4/8] lib/igt_kms: Rework connector properties to be more atomic, v2 Maarten Lankhorst
2017-09-27 18:16 ` [PATCH i-g-t v2 5/8] lib/igt_kms: Rework plane " Maarten Lankhorst
2017-09-28 10:28   ` [PATCH i-g-t v2 5/8] lib/igt_kms: Rework plane properties to be more atomic, v3 Maarten Lankhorst
2017-09-28 11:01     ` [PATCH i-g-t v2 5/8] lib/igt_kms: Rework plane properties to be more atomic, v4 Maarten Lankhorst
2017-09-29  9:52       ` [PATCH i-g-t] lib/igt_kms: Rework pipe properties to be more atomic, v4.1 Maarten Lankhorst
2017-09-27 18:16 ` [PATCH i-g-t v2 6/8] lib/igt_kms: Rework pipe properties to be more atomic, v2 Maarten Lankhorst
2017-09-28 10:28   ` [PATCH i-g-t v2 6/8] lib/igt_kms: Rework pipe properties to be more atomic, v3 Maarten Lankhorst
2017-09-29  6:50     ` [PATCH i-g-t] lib/igt_kms: Rework pipe properties to be more atomic, v4 Maarten Lankhorst
2017-09-27 18:16 ` [PATCH i-g-t v2 7/8] igt/kms_rotation_crc : Fix flip tests for sprite plane Maarten Lankhorst
2017-09-27 18:16 ` [PATCH i-g-t v2 8/8] tests: Rename kms_pipe_color to kms_color Maarten Lankhorst
2017-09-29 10:00   ` Mika Kahola [this message]
2017-09-27 18:39 ` ✓ Fi.CI.BAT: success for lib/igt_kms: Convert properties to be more atomic-like. (rev2) Patchwork
2017-09-27 22:51 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-09-28 10:50 ` ✓ Fi.CI.BAT: success for lib/igt_kms: Convert properties to be more atomic-like. (rev4) Patchwork
2017-09-28 11:23 ` ✓ Fi.CI.BAT: success for lib/igt_kms: Convert properties to be more atomic-like. (rev5) Patchwork
2017-09-28 11:47 ` ✗ Fi.CI.IGT: failure for lib/igt_kms: Convert properties to be more atomic-like. (rev4) Patchwork
2017-09-28 12:34 ` ✗ Fi.CI.IGT: failure for lib/igt_kms: Convert properties to be more atomic-like. (rev5) Patchwork
2017-09-28 13:01 ` ✗ Fi.CI.IGT: failure for lib/igt_kms: Convert properties to be more atomic-like. (rev4) Patchwork
2017-09-28 13:04 ` ✗ Fi.CI.IGT: failure for lib/igt_kms: Convert properties to be more atomic-like. (rev5) Patchwork
2017-09-28 16:09 ` ✗ Fi.CI.IGT: failure for lib/igt_kms: Convert properties to be more atomic-like. (rev2) Patchwork
2017-09-29  6:58 ` ✗ Fi.CI.BAT: failure for lib/igt_kms: Convert properties to be more atomic-like. (rev6) Patchwork

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=1506679204.3274.18.camel@intel.com \
    --to=mika.kahola@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox