public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 7/8] tests/intel/kms_pipe_stress: Eliminate double display.drm_fd initialization
Date: Tue, 13 Jan 2026 16:39:26 +0200	[thread overview]
Message-ID: <9f4927fe7229385e1ccbf244ea4f3c0290fedd43@intel.com> (raw)
In-Reply-To: <20260113120439.12577-8-ville.syrjala@linux.intel.com>

On Tue, 13 Jan 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Stop initializing display.drm_fd twice. The first one
> is done explicitly and the second time is done by
> igt_display_require(). Just rely on igt_display_require().
>
> Note that a bunch of other tests do still do something similar

-do

> by completely omitting the local fd varaible/member and just

*variable

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

> using display.drm_fd everywhere. It's a somewhat strange way
> to do things, but I decided to leave those alone at least for
> now.
>
> Done with cocci:
>  #include "scripts/iterators.cocci"
>
> @@
> expression DISPLAY;
> expression FD, E;
> @@
> - FD = DISPLAY.drm_fd = E;
> + FD = E;
> ...
> (
> igt_display_require(&DISPLAY, FD)
> |
> igt_display_require(&DISPLAY,
> -	DISPLAY.drm_fd
> +	FD
> 	)
> )
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  tests/intel/kms_pipe_stress.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/intel/kms_pipe_stress.c b/tests/intel/kms_pipe_stress.c
> index e8e01556ba25..33ccac9fcee3 100644
> --- a/tests/intel/kms_pipe_stress.c
> +++ b/tests/intel/kms_pipe_stress.c
> @@ -862,11 +862,11 @@ int igt_main() {
>  	uint8_t format_idx = 0, tiling_idx = 0;
>  
>  	igt_fixture() {
> -		data.drm_fd = data.display.drm_fd = drm_open_driver_master(DRIVER_INTEL | DRIVER_XE);
> +		data.drm_fd = drm_open_driver_master(DRIVER_INTEL | DRIVER_XE);
>  
>  		kmstest_set_vt_graphics_mode();
>  
> -		igt_display_require(&data.display, data.display.drm_fd);
> +		igt_display_require(&data.display, data.drm_fd);
>  		igt_require(data.display.is_atomic);
>  		igt_display_require_output(&data.display);
>  		data.devid = intel_get_drm_devid(data.drm_fd);

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-01-13 14:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 12:04 [PATCH i-g-t 0/8] Some cleanups etc Ville Syrjala
2026-01-13 12:04 ` [PATCH i-g-t 1/8] tests/kms_plane_cursor: s/or/rect/ Ville Syrjala
2026-01-13 14:31   ` Jani Nikula
2026-01-13 12:04 ` [PATCH i-g-t 2/8] tests/intel/i915_pm_rpm: Nuke bogus NULL check Ville Syrjala
2026-01-13 14:31   ` Jani Nikula
2026-01-13 12:04 ` [PATCH i-g-t 3/8] tests/kms_rotation_crc: s/0/PIPE_A/ Ville Syrjala
2026-01-13 14:32   ` Jani Nikula
2026-01-13 12:04 ` [PATCH i-g-t 4/8] lib/kms: Nuke pipe_select() Ville Syrjala
2026-01-13 14:32   ` Jani Nikula
2026-01-13 12:04 ` [PATCH i-g-t 5/8] lib/kms: Simplify kmstest_get_vbl_flag() Ville Syrjala
2026-01-13 14:33   ` Jani Nikula
2026-01-13 12:04 ` [PATCH i-g-t 6/8] tests/kms_async_flips: Use designated initializers in wait_for_vblank() Ville Syrjala
2026-01-13 14:37   ` Jani Nikula
2026-01-13 12:04 ` [PATCH i-g-t 7/8] tests/intel/kms_pipe_stress: Eliminate double display.drm_fd initialization Ville Syrjala
2026-01-13 14:39   ` Jani Nikula [this message]
2026-01-13 12:04 ` [PATCH i-g-t 8/8] lib/kms: Turn igt_pipe_connector_valid() into a function Ville Syrjala
2026-01-13 14:41   ` Jani Nikula
2026-01-13 15:01 ` ✓ Xe.CI.BAT: success for Some cleanups etc Patchwork
2026-01-13 15:18 ` ✓ i915.CI.BAT: " Patchwork
2026-01-13 22:00 ` ✗ i915.CI.Full: failure " Patchwork
2026-01-13 23:14 ` ✗ Xe.CI.Full: " Patchwork
2026-01-15 15:09 ` ✓ Xe.CI.BAT: success for Some cleanups etc. (rev2) Patchwork
2026-01-15 15:17 ` ✓ i915.CI.BAT: " Patchwork
2026-01-15 17:26 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-15 18:22 ` ✗ i915.CI.Full: " 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=9f4927fe7229385e1ccbf244ea4f3c0290fedd43@intel.com \
    --to=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox