From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 0/3] lib/kms: only keep valid igt_crtc_t around
Date: Tue, 31 Mar 2026 10:50:29 +0300 [thread overview]
Message-ID: <91b83f2ab9e75e887aeca01adff0647299a42987@intel.com> (raw)
In-Reply-To: <acr_yGTKiF9n2jVH@intel.com>
On Tue, 31 Mar 2026, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Mon, Mar 30, 2026 at 10:36:27AM +0300, Jani Nikula wrote:
>> Only keep valid igt_crtc_t in display->crtcs[] and make
>> igt_display_n_crtcs() return the actual number of CRTCs on the device.
>>
>> Jani Nikula (3):
>> lib/kms: start returning NULL for invalid pipes from
>> igt_crtc_for_pipe()
>> lib/kms: use a for_each_crtc() loop in igt_crtc_for_pipe()
>> lib/kms: only keep valid CRTCs in display->crtcs[]
>
> Series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks, pushed.
This pretty much marks the end of the pipe <-> CRTC index deconflation
all over IGT. \o/
Sure, there's still cleanups here and there that could be done, but the
bulk of the functional changes is there.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-03-31 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 7:36 [PATCH i-g-t 0/3] lib/kms: only keep valid igt_crtc_t around Jani Nikula
2026-03-30 7:36 ` [PATCH i-g-t 1/3] lib/kms: start returning NULL for invalid pipes from igt_crtc_for_pipe() Jani Nikula
2026-03-30 7:36 ` [PATCH i-g-t 2/3] lib/kms: use a for_each_crtc() loop in igt_crtc_for_pipe() Jani Nikula
2026-03-30 7:36 ` [PATCH i-g-t 3/3] lib/kms: only keep valid CRTCs in display->crtcs[] Jani Nikula
2026-03-30 22:57 ` [PATCH i-g-t 0/3] lib/kms: only keep valid igt_crtc_t around Ville Syrjälä
2026-03-31 7:50 ` Jani Nikula [this message]
2026-03-31 8:49 ` Saarinen, Jani
2026-03-30 23:52 ` ✓ i915.CI.BAT: success for " Patchwork
2026-03-31 0:00 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-31 3:29 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-31 5:58 ` ✓ 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=91b83f2ab9e75e887aeca01adff0647299a42987@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