From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [CI] drm/i915/display: change pipe allocation order for discrete platforms
Date: Mon, 09 Feb 2026 17:10:42 +0200 [thread overview]
Message-ID: <cf64c6a82c6ee7275b6e4099c6717c0039367cbe@intel.com> (raw)
In-Reply-To: <20260206123715.234245-1-jani.nikula@intel.com>
On Fri, 06 Feb 2026, Jani Nikula <jani.nikula@intel.com> wrote:
> @@ -415,6 +438,8 @@ int intel_crtc_init(struct intel_display *display)
> INTEL_NUM_PIPES(display), str_plural(INTEL_NUM_PIPES(display)));
>
> for_each_pipe(display, pipe) {
> + pipe = reorder_pipe(display, pipe);
> +
This assignment screws up the loop variable and everything
breaks. *facepalm*.
See [1] instead.
[1] https://lore.kernel.org/r/20260209141657.629872-1-jani.nikula@intel.com
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-02-09 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 12:37 [CI] drm/i915/display: change pipe allocation order for discrete platforms Jani Nikula
2026-02-06 13:02 ` ✓ CI.KUnit: success for drm/i915/display: change pipe allocation order for discrete platforms (rev2) Patchwork
2026-02-06 14:12 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-02-07 14:26 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-09 15:10 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-16 12:18 [CI] drm/i915/display: change pipe allocation order for discrete platforms Jani Nikula
2026-03-30 11:37 ` Jani Nikula
2026-03-30 15:35 ` Ville Syrjälä
2026-04-02 9:43 ` Jani Nikula
2026-04-02 10:18 ` Ville Syrjälä
2026-04-02 13:33 ` Ville Syrjälä
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=cf64c6a82c6ee7275b6e4099c6717c0039367cbe@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox