From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 0/3] lib/kms: fix a CRTC index and pipe mask mixup
Date: Tue, 10 Mar 2026 11:15:22 +0200 [thread overview]
Message-ID: <aa_hKq8zi6tdcva6@intel.com> (raw)
In-Reply-To: <cover.1773059939.git.jani.nikula@intel.com>
On Mon, Mar 09, 2026 at 02:40:11PM +0200, Jani Nikula wrote:
> Clean up __igt_pipe_populate_outputs() to use CRTC indexes where
> possible, and fix a CRTC index vs. pipe mask confusion.
>
> Jani Nikula (3):
> igt/kms: add some braces for clarity in __igt_pipe_populate_outputs()
> lib/kms: use for_each_crtc() in __igt_pipe_populate_outputs()
> lib/kms: avoid mixing CRTC index and pipe masks in
> __igt_pipe_populate_outputs()
Series is
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> lib/igt_kms.c | 39 +++++++++++++++++++++------------------
> 1 file changed, 21 insertions(+), 18 deletions(-)
>
> --
> 2.47.3
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-03-10 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 12:40 [PATCH i-g-t 0/3] lib/kms: fix a CRTC index and pipe mask mixup Jani Nikula
2026-03-09 12:40 ` [PATCH i-g-t 1/3] igt/kms: add some braces for clarity in __igt_pipe_populate_outputs() Jani Nikula
2026-03-09 12:40 ` [PATCH i-g-t 2/3] lib/kms: use for_each_crtc() " Jani Nikula
2026-03-09 12:40 ` [PATCH i-g-t 3/3] lib/kms: avoid mixing CRTC index and pipe masks " Jani Nikula
2026-03-09 20:38 ` ✓ Xe.CI.BAT: success for lib/kms: fix a CRTC index and pipe mask mixup Patchwork
2026-03-09 20:54 ` ✓ i915.CI.BAT: " Patchwork
2026-03-10 1:06 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-10 5:55 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-10 9:15 ` Ville Syrjälä [this message]
2026-03-10 9:35 ` [PATCH i-g-t 0/3] " Jani Nikula
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=aa_hKq8zi6tdcva6@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@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