From: Julia Filipchuk <julia.filipchuk@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2 2/3] Revert "drm/xe/xe3p_xpc: Enable Indirect Ring State for xe3p_xpc"
Date: Fri, 6 Feb 2026 11:22:49 -0800 [thread overview]
Message-ID: <305535b0-b988-4dd4-be85-22f88565a04d@intel.com> (raw)
In-Reply-To: <b1ef6434-add7-47db-9c16-9de738e99c73@intel.com>
On 2/2/2026 5:03 PM, Daniele Ceraolo Spurio wrote:
> This needs an explanation on why this revert is occurring. Also, This patch and
> the next one should be swapped, otherwise if a bisect ends up on this patch the
> feature will be disabled.
Will add explanations. Great note on the corrected order for proper bisect
functionality!
next prev parent reply other threads:[~2026-02-06 19:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 20:50 [PATCH v2 0/3] drm/xe: Enable Wa_14025515070, Enable indirect ring state for XE2+ Julia Filipchuk
2026-01-30 20:50 ` [PATCH v2 1/3] drm/xe: Enable Wa_14025515070 Julia Filipchuk
2026-02-03 1:02 ` Daniele Ceraolo Spurio
2026-02-03 1:37 ` Daniele Ceraolo Spurio
2026-02-03 23:43 ` Daniele Ceraolo Spurio
2026-02-06 19:04 ` Julia Filipchuk
2026-02-06 19:02 ` Julia Filipchuk
2026-01-30 20:50 ` [PATCH v2 2/3] Revert "drm/xe/xe3p_xpc: Enable Indirect Ring State for xe3p_xpc" Julia Filipchuk
2026-02-03 1:03 ` Daniele Ceraolo Spurio
2026-02-06 19:22 ` Julia Filipchuk [this message]
2026-01-30 20:50 ` [PATCH v2 3/3] Reapply "drm/xe/xe2: Enable Indirect Ring State support for Xe2" Julia Filipchuk
2026-02-03 1:04 ` Daniele Ceraolo Spurio
2026-01-30 21:06 ` ✗ CI.checkpatch: warning for drm/xe: Enable Wa_14025515070, Enable indirect ring state for XE2+ (rev2) Patchwork
2026-01-30 21:08 ` ✓ CI.KUnit: success " Patchwork
2026-01-30 21:44 ` ✓ Xe.CI.BAT: " 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=305535b0-b988-4dd4-be85-22f88565a04d@intel.com \
--to=julia.filipchuk@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--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