Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <Intel-Xe@lists.freedesktop.org>
Subject: Re: [PATCH 0/3] Update to GuC 70.19.2 and add LNL
Date: Fri, 2 Feb 2024 10:51:36 -0800	[thread overview]
Message-ID: <2cd956b3-bccb-4423-be46-435125343449@intel.com> (raw)
In-Reply-To: <njcmjcrd32ztgxa7gwmgsmhszwsm5je3ojv7mfvpkmm5s7dfep@mqy2hfmadmif>

On 2/2/2024 08:53, Lucas De Marchi wrote:
> On Thu, Feb 01, 2024 at 11:30:47PM -0800, John.C.Harrison@Intel.com 
> wrote:
>> From: John Harrison <John.C.Harrison@Intel.com>
>>
>> Update to the latest GuC release including the first release for LNL.
>> Also include the patch version in the expectation check as it can be
>> important.
>>
>> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>
> For CI to be able to test this series you have to do:
>
> a) be on top of drm-tip, not drm-xe-next
Is this instruction special for this particular patch set because of the 
for-ci conflict? The wiki page is definitely still saying to base 
patches on drm-xe-next from fdo:/drm/xe/kernel.git.

Is there an Xe specific repo for an Xe specific drm-tip? Or are you 
meaning the genuine drm-tip from fdo:/drm-tip?

John.


> b) revert the commits from topic branches that would conflict
>
>     e4cfe0cd9819 ("drm/xe/guc: define LNL FW")     6fed16fd875e 
> ("drm/xe/guc: define PVC FW")
>
> c) Add the patches you have in this series
> d) Add back 6fed16fd875e with conflict resolved and mention that
>    specific patch is for topic/xe-for-CI only.
>
> Lucas De Marchi
>
>>
>>
>> John Harrison (3):
>>  drm/xe/uc: Include patch version in expectations
>>  drm/xe/guc: Update to GuC firmware 70.19.2
>>  drm/xe/guc: Add support for LNL firmware
>>
>> drivers/gpu/drm/xe/xe_uc_fw.c | 50 ++++++++++++++++++++---------------
>> 1 file changed, 28 insertions(+), 22 deletions(-)
>>
>> -- 
>> 2.43.0
>>


  reply	other threads:[~2024-02-02 18:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  7:30 [PATCH 0/3] Update to GuC 70.19.2 and add LNL John.C.Harrison
2024-02-02  7:30 ` [PATCH 1/3] drm/xe/uc: Include patch version in expectations John.C.Harrison
2024-02-02 16:48   ` Lucas De Marchi
2024-02-02  7:30 ` [PATCH 2/3] drm/xe/guc: Update to GuC firmware 70.19.2 John.C.Harrison
2024-02-02 16:56   ` Lucas De Marchi
2024-02-02 20:00     ` John Harrison
2024-02-02  7:30 ` [PATCH 3/3] drm/xe/guc: Add support for LNL firmware John.C.Harrison
2024-02-02 17:00   ` Lucas De Marchi
2024-02-02  7:36 ` ✗ CI.Patch_applied: failure for Update to GuC 70.19.2 and add LNL Patchwork
2024-02-02 16:53 ` [PATCH 0/3] " Lucas De Marchi
2024-02-02 18:51   ` John Harrison [this message]
2024-02-02 19:35     ` Lucas De Marchi
2024-02-02 19:53       ` John Harrison

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=2cd956b3-bccb-4423-be46-435125343449@intel.com \
    --to=john.c.harrison@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