Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH xe-for-ci] fixup! drm/xe/guc: Pre-release GuC firmware v70.29.2 for PVC
Date: Fri,  9 Aug 2024 14:34:52 -0300	[thread overview]
Message-ID: <20240809173459.78732-1-gustavo.sousa@intel.com> (raw)

We are moving away from the intel-for-ci branch in drm/firmware[1] and
we sill use intel-staging for all public firmware, those under test and
those that get upstreamed to linux-firmware.

We recently pushed a commit that makes the GuC v70.29.2 also available
in intel-staging with the "intel-ci/" prefix removed. Let's now update
the kernel side by removing the prefix in the firmware definition as
well.

[1] https://gitlab.freedesktop.org/drm/firmware

Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
---
 drivers/gpu/drm/xe/xe_uc_fw.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
index 41c4ac6ba42a..d4809ec7d634 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw.c
+++ b/drivers/gpu/drm/xe/xe_uc_fw.c
@@ -109,7 +109,7 @@ struct fw_blobs_by_type {
 	fw_def(BATTLEMAGE,	major_ver(xe,	guc,	bmg,	70, 29, 2))	\
 	fw_def(LUNARLAKE,	major_ver(xe,	guc,	lnl,	70, 29, 2))	\
 	fw_def(METEORLAKE,	major_ver(i915,	guc,	mtl,	70, 29, 2))	\
-	fw_def(PVC,		mmp_ver(intel-ci/xe, guc, pvc,	70, 29, 2))	\
+	fw_def(PVC,		mmp_ver(xe,	guc,	pvc,	70, 29, 2))	\
 	fw_def(DG2,		major_ver(i915,	guc,	dg2,	70, 29, 2))	\
 	fw_def(DG1,		major_ver(i915,	guc,	dg1,	70, 29, 2))	\
 	fw_def(ALDERLAKE_N,	major_ver(i915,	guc,	tgl,	70, 29, 2))	\
-- 
2.45.2


             reply	other threads:[~2024-08-09 17:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 17:34 Gustavo Sousa [this message]
2024-08-09 17:38 ` [PATCH xe-for-ci] fixup! drm/xe/guc: Pre-release GuC firmware v70.29.2 for PVC Lucas De Marchi
2024-08-09 18:37 ` ✓ CI.Patch_applied: success for " Patchwork
2024-08-09 18:37 ` ✓ CI.checkpatch: " Patchwork
2024-08-09 18:38 ` ✓ CI.KUnit: " Patchwork
2024-08-09 18:50 ` ✓ CI.Build: " Patchwork
2024-08-09 18:52 ` ✓ CI.Hooks: " Patchwork
2024-08-09 18:53 ` ✓ CI.checksparse: " Patchwork
2024-08-09 19:14 ` ✓ CI.BAT: " Patchwork
2024-08-09 22:52 ` ✗ CI.FULL: failure " Patchwork
2024-08-09 23:37   ` Lucas De Marchi

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=20240809173459.78732-1-gustavo.sousa@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@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