From: Jani Nikula <jani.nikula@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [CI 0/5] tests: some igt_crtc_for_pipe() reduction
Date: Tue, 24 Mar 2026 11:01:46 +0200 [thread overview]
Message-ID: <cover.1774342824.git.jani.nikula@intel.com> (raw)
Picked up some patches from [1] for CI results and merging.
[1] https://lore.kernel.org/r/cover.1774002591.git.jani.nikula@intel.com
Jani Nikula (5):
tests/kms_bw: fix misleading indent
tests/kms_bw: clarify what's going on with proper variable naming
tests/kms_bw: avoid igt_crtc_for_pipe() and crtc->pipe usage
tests/kms_explicit_fence: store igt_crtc_t* instead of pipe in data
lib/kms: convert igt_crtc_for_pipe() into a proper function
lib/igt_kms.c | 8 +++++++
lib/igt_kms.h | 8 +------
tests/kms_bw.c | 48 ++++++++++++++++++++------------------
tests/kms_explicit_fence.c | 14 +++++------
4 files changed, 41 insertions(+), 37 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-24 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 9:01 Jani Nikula [this message]
2026-03-24 9:01 ` [CI 1/5] tests/kms_bw: fix misleading indent Jani Nikula
2026-03-24 9:01 ` [CI 2/5] tests/kms_bw: clarify what's going on with proper variable naming Jani Nikula
2026-03-24 9:01 ` [CI 3/5] tests/kms_bw: avoid igt_crtc_for_pipe() and crtc->pipe usage Jani Nikula
2026-03-24 9:01 ` [CI 4/5] tests/kms_explicit_fence: store igt_crtc_t* instead of pipe in data Jani Nikula
2026-03-24 9:01 ` [CI 5/5] lib/kms: convert igt_crtc_for_pipe() into a proper function Jani Nikula
2026-03-24 12:49 ` ✓ Xe.CI.BAT: success for tests: some igt_crtc_for_pipe() reduction Patchwork
2026-03-24 13:10 ` ✓ i915.CI.BAT: " Patchwork
2026-03-24 21:36 ` ✓ i915.CI.Full: " Patchwork
2026-03-25 0:27 ` ✗ Xe.CI.FULL: failure " 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=cover.1774342824.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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.