From: Jani Nikula <jani.nikula@intel.com>
To: imre.deak@intel.com, Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ i915.CI.Full: failure for drm/i915/dp: Fix 128b/132b modeset issues
Date: Wed, 19 Feb 2025 18:27:44 +0200 [thread overview]
Message-ID: <87tt8pnblr.fsf@intel.com> (raw)
In-Reply-To: <Z7Xa3z7wdI_b7Fa0@ideak-desk.fi.intel.com>
On Wed, 19 Feb 2025, Imre Deak <imre.deak@intel.com> wrote:
> Thanks for the ack/review, patchset pushed to drm-intel-fixes, adding
> the bspec references to patch 1.
Uh, so you did, but committers aren't supposed to apply patches directly
to drm-intel-fixes, only drm-intel-next. Maintainers cherry-pick to
fixes.
Rodrigo's maintaining fixes now. Would it be the simplest to just remove
the commits from fixes, apply to drm-intel-next instead, and then
cherry-pick?
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-02-19 16:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 22:38 [PATCH 0/2] drm/i915/dp: Fix 128b/132b modeset issues Imre Deak
2025-02-17 22:38 ` [PATCH 1/2] drm/i915/dp: Fix error handling during 128b/132b link training Imre Deak
2025-02-18 12:51 ` Jani Nikula
2025-02-18 13:06 ` Imre Deak
2025-02-17 22:38 ` [PATCH 2/2] drm/i915/dp: Fix disabling the transcoder function in 128b/132b mode Imre Deak
2025-02-18 13:03 ` Jani Nikula
2025-02-18 13:15 ` Imre Deak
2025-02-17 22:43 ` ✓ CI.Patch_applied: success for drm/i915/dp: Fix 128b/132b modeset issues Patchwork
2025-02-17 22:43 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-17 22:44 ` ✓ CI.KUnit: success " Patchwork
2025-02-17 23:01 ` ✓ CI.Build: " Patchwork
2025-02-17 23:01 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2025-02-17 23:01 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-02-17 23:03 ` ✓ CI.Hooks: success " Patchwork
2025-02-17 23:04 ` ✓ CI.checksparse: " Patchwork
2025-02-17 23:18 ` ✓ i915.CI.BAT: " Patchwork
2025-02-17 23:24 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-18 4:36 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-19 13:21 ` Imre Deak
2025-02-19 16:27 ` Jani Nikula [this message]
2025-02-19 17:09 ` Rodrigo Vivi
2025-02-19 17:49 ` Imre Deak
2025-02-18 16:27 ` ✗ Xe.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=87tt8pnblr.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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 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.