From: Jani Nikula <jani.nikula@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
Vitaly Prosyak <vitaly.prosyak@amd.com>,
Alex Hung <alex.hung@amd.com>
Subject: Re: [PATCH i-g-t 0/7] tests: lots of s/crtc->pipe/crtc->crtc_index/
Date: Tue, 24 Mar 2026 11:09:10 +0200 [thread overview]
Message-ID: <c066ab16457a8e089bf9bed8d5624877e256282d@intel.com> (raw)
In-Reply-To: <cover.1774005763.git.jani.nikula@intel.com>
On Fri, 20 Mar 2026, Jani Nikula <jani.nikula@intel.com> wrote:
> Do a bunch of s/crtc->pipe/crtc->crtc_index/ where the crtc->pipe isn't
> actually needed or relevant, e.g. basically all of amdgpu tests.
>
> Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>
> Cc: Alex Hung <alex.hung@amd.com>
Ping, this should be trivial and quick to review, and I'd like to get
this moving.
BR,
Jani.
>
> Jani Nikula (7):
> tests/amdgpu/amd_plane: s/crtc->pipe/crtc->crtc_index/
> tests/amdgpu/amd_dp_dsc: s/crtc->pipe/crtc->crtc_index/
> tests/amdgpu/amd_subvp: s/crtc->pipe/crtc->crtc_index/
> tests/amdgpu/amd_hotplug: s/crtc->pipe/crtc->crtc_index/
> tests/amdgpu/amd_multidisplay_modeset: s/crtc->pipe/crtc->crtc_index/
> tests/amdgpu/amd_vrr_range: s/crtc->pipe/crtc->crtc_index/
> tests/kms_atomic_transition: s/crtc->pipe/crtc->crtc_index/
>
> tests/amdgpu/amd_dp_dsc.c | 142 ++++++++++++------------
> tests/amdgpu/amd_hotplug.c | 52 +++++----
> tests/amdgpu/amd_multidisplay_modeset.c | 30 ++---
> tests/amdgpu/amd_plane.c | 27 ++---
> tests/amdgpu/amd_subvp.c | 16 +--
> tests/amdgpu/amd_vrr_range.c | 4 +-
> tests/kms_atomic_transition.c | 18 +--
> 7 files changed, 144 insertions(+), 145 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-03-24 9:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 11:24 [PATCH i-g-t 0/7] tests: lots of s/crtc->pipe/crtc->crtc_index/ Jani Nikula
2026-03-20 11:24 ` [PATCH i-g-t 1/7] tests/amdgpu/amd_plane: s/crtc->pipe/crtc->crtc_index/ Jani Nikula
2026-03-20 11:24 ` [PATCH i-g-t 2/7] tests/amdgpu/amd_dp_dsc: s/crtc->pipe/crtc->crtc_index/ Jani Nikula
2026-03-20 11:24 ` [PATCH i-g-t 3/7] tests/amdgpu/amd_subvp: s/crtc->pipe/crtc->crtc_index/ Jani Nikula
2026-03-20 11:24 ` [PATCH i-g-t 4/7] tests/amdgpu/amd_hotplug: s/crtc->pipe/crtc->crtc_index/ Jani Nikula
2026-03-20 11:24 ` [PATCH i-g-t 5/7] tests/amdgpu/amd_multidisplay_modeset: s/crtc->pipe/crtc->crtc_index/ Jani Nikula
2026-03-20 11:24 ` [PATCH i-g-t 6/7] tests/amdgpu/amd_vrr_range: s/crtc->pipe/crtc->crtc_index/ Jani Nikula
2026-03-20 11:24 ` [PATCH i-g-t 7/7] tests/kms_atomic_transition: s/crtc->pipe/crtc->crtc_index/ Jani Nikula
2026-03-20 14:56 ` ✓ Xe.CI.BAT: success for tests: lots of s/crtc->pipe/crtc->crtc_index/ Patchwork
2026-03-20 15:10 ` ✓ i915.CI.BAT: " Patchwork
2026-03-21 6:45 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-21 15:06 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-24 9:09 ` Jani Nikula [this message]
2026-03-24 17:45 ` [PATCH i-g-t 0/7] " Alex Hung
2026-03-24 17:54 ` Jani Nikula
2026-03-24 18:02 ` Alex Hung
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=c066ab16457a8e089bf9bed8d5624877e256282d@intel.com \
--to=jani.nikula@intel.com \
--cc=alex.hung@amd.com \
--cc=aurabindo.pillai@amd.com \
--cc=harry.wentland@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=vitaly.prosyak@amd.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