From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Julia Filipchuk <julia.filipchuk@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH 0/3] [drm-xe:topic/xe-for-CI] Use GuC firmware 70.68.0 for pre-release platforms.
Date: Fri, 5 Jun 2026 18:15:13 -0400 [thread overview]
Message-ID: <aiNKcXnMTfOJvrbc@intel.com> (raw)
In-Reply-To: <20260604205325.1977872-5-julia.filipchuk@intel.com>
On Thu, Jun 04, 2026 at 01:51:35PM -0700, Julia Filipchuk wrote:
> Use GuC version 70.68.0 for NVL-S, CRI, NVL-P.
>
> Patches are intended to be merged into drm-xe:/topic/xe-for-CI branch.
Pushed, thanks for the updates.
for the record, the other approach with the revert + new patch is easier.
So the maintainer can just:
$ b4 <header>
$ git rebase -i <somehash>
# Remove original patches and revert
$ dim push -f
The fixup flow is something like:
$ b4 <header>
$ git rebase -i --autosquash <somehash>
# Fix each patch conflict;
# For each patch:
$ git rebase --continue
$ dim push
For me it was simple because I use a git-truce wiggle based script to deal
with conflicts and easy obvious conflicts like that it is just to
$ b4 <header>
$ git rebase -i --autosquash <somehash>
# For each patch:
$ git-truce
$ git rebase --continue
$ dim push
But as I told, just for the record. It was easy to me.
Thanks for doing the hardest part and the diligence with the validation and all!
Thanks,
Rodrigo.
>
> Platforms NVL-S, CRI, NVL-P are not merged to upstream at present. The
> GuC definitions for those only exist in the for-ci topic branch
> drm-xe:topic/xe-for-ci. This patch set provides fixup commits to bump
> the versions.
>
> Julia INTEL (3):
> fixup! topic/xe-for-CI: Define GuC firmware for NVL-S
> fixup! topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI
> fixup! topic/xe-for-CI: Define GuC firmware for NVL-P
>
> drivers/gpu/drm/xe/xe_uc_fw.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.51.0
>
prev parent reply other threads:[~2026-06-05 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 20:51 [PATCH 0/3] [drm-xe:topic/xe-for-CI] Use GuC firmware 70.68.0 for pre-release platforms Julia Filipchuk
2026-06-04 20:51 ` [PATCH 1/3] fixup! topic/xe-for-CI: Define GuC firmware for NVL-S Julia Filipchuk
2026-06-04 20:51 ` [PATCH 2/3] fixup! topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI Julia Filipchuk
2026-06-04 20:51 ` [PATCH 3/3] fixup! topic/xe-for-CI: Define GuC firmware for NVL-P Julia Filipchuk
2026-06-04 21:11 ` ✓ CI.KUnit: success for Use GuC firmware 70.68.0 for pre-release platforms Patchwork
2026-06-04 21:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-05 13:09 ` ✓ Xe.CI.FULL: " Patchwork
2026-06-05 22:15 ` Rodrigo Vivi [this message]
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=aiNKcXnMTfOJvrbc@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=julia.filipchuk@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.