Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Julia Filipchuk" <julia.filipchuk@intel.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/1] fixup! drm/xe/nvlp: Define GuC firmware for NVL-P
Date: Thu, 12 Mar 2026 16:10:14 -0300	[thread overview]
Message-ID: <87h5qk6ezt.fsf@intel.com> (raw)
In-Reply-To: <7eceb569-f048-403e-abc4-2b741d51dd7d@intel.com>

Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> writes:

> We usually specify it in the patch tag when the patches are meant for 
> topic/xe-for-ci
>
> On 3/3/2026 1:36 PM, Gustavo Sousa wrote:
>> Update GuC version for NVL-P to v70.60.0.
>>
>> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
>
> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

Thanks, Daniele!

I think now we need help from an Xe maintainer on applying this to topic/xe-for-CI.

--
Gustavo Sousa

>
> Daniele
>
>> ---
>>   drivers/gpu/drm/xe/xe_uc_fw.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
>> index 60c82b920f47..9aa8deefa6c4 100644
>> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
>> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
>> @@ -115,8 +115,8 @@ struct fw_blobs_by_type {
>>   #define XE_GT_TYPE_ANY XE_GT_TYPE_UNINITIALIZED
>>   
>>   #define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver)					\
>> -	fw_def(NOVALAKE_P,	GT_TYPE_MAIN,	mmp_ver(xe,	guc,	nvlpg,	70, 55, 4))	\
>> -	fw_def(NOVALAKE_P,	GT_TYPE_MEDIA,	mmp_ver(xe,	guc,	nvlpm,	70, 55, 4))	\
>> +	fw_def(NOVALAKE_P,	GT_TYPE_MAIN,	mmp_ver(xe,	guc,	nvlpg,	70, 60, 0))	\
>> +	fw_def(NOVALAKE_P,	GT_TYPE_MEDIA,	mmp_ver(xe,	guc,	nvlpm,	70, 60, 0))	\
>>   	fw_def(CRESCENTISLAND,	GT_TYPE_ANY,	mmp_ver(xe,	guc,	cri,	70, 55, 4))	\
>>   	fw_def(NOVALAKE_S,	GT_TYPE_ANY,	mmp_ver(xe,	guc,	nvl,	70, 55, 4))	\
>>   	fw_def(PANTHERLAKE,	GT_TYPE_ANY,	major_ver(xe,	guc,	ptl,	70, 54, 0))	\

  reply	other threads:[~2026-03-12 19:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 21:36 [PATCH 0/1] [topic/xe-for-CI] Update NVL-P GuC to v70.60.0 Gustavo Sousa
2026-03-03 21:36 ` [PATCH 1/1] fixup! drm/xe/nvlp: Define GuC firmware for NVL-P Gustavo Sousa
2026-03-06 19:03   ` Daniele Ceraolo Spurio
2026-03-12 19:10     ` Gustavo Sousa [this message]
2026-03-13  0:55       ` Rodrigo Vivi
2026-03-03 22:10 ` ✓ CI.KUnit: success for Update NVL-P GuC to v70.60.0 Patchwork
2026-03-03 22:45 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-04 11:08 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-04 13:00 ` Patchwork
2026-03-06  7:08 ` ✓ CI.KUnit: success for Update NVL-P GuC to v70.60.0 (rev2) Patchwork
2026-03-06  8:04 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-07  7:14 ` ✗ 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=87h5qk6ezt.fsf@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=julia.filipchuk@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.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