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 11:53:45 -0800 [thread overview]
Message-ID: <de3159f5-c992-4ee0-b420-90b86c5464a1@intel.com> (raw)
In-Reply-To: <pm77ns5mf7s4f4dk7jsf4c424bi5evvtvsfpnvf26svluys6ry@fv6lo3wbqh37>
On 2/2/2024 11:35, Lucas De Marchi wrote:
> On Fri, Feb 02, 2024 at 10:51:36AM -0800, John Harrison wrote:
>> 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
>
> If you're talking about our internal documentation, it's
> outdated since drm-xe-next got merged upstream. Documentation for
> drm-xe-next is now maintained upstream as part of drm-tip too.
It would be useful if the internal doc could be updated to reflect this
change. You can't really complain at people when they are correctly
following instructions!
>
>> patches on drm-xe-next from fdo:/drm/xe/kernel.git.
>
> patches targeting xe are *merged* through drm-xe-next. Usually. And it
> usually applies fine if you are on top of drm-tip or drm-xe-next, but
> not in this case as we have the topic branch that conflicts.
>
> Since when we got merged, drm-xe-next is "just one more branch" that
> forms drm-tip:
>
> https://drm.pages.freedesktop.org/maintainer-tools/drm-xe.html
>
> and drm-tip, as an integration branch, is the merge of all its component
> branches that is done on every push to any component branch.
I am aware of how drm-tip is constructed. I just being confused by the
conflicting documentation.
>
>>
>> Is there an Xe specific repo for an Xe specific drm-tip? Or are you
>> meaning the genuine drm-tip from fdo:/drm-tip?
>
> not sure I understand the question, but I meant the one and only
> drm-tip as per doc above.
Okay. That's what I meant. I just wasn't sure if there was some new, Xe
specific version of that entire process alongside the regular one. As I
said, the internal doc describes a very Xe specific process so it is
confusing as to how much is Xe only versus how much is now just regular drm.
John.
>
> Lucas De Marchi
prev parent reply other threads:[~2024-02-02 19:53 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
2024-02-02 19:35 ` Lucas De Marchi
2024-02-02 19:53 ` John Harrison [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=de3159f5-c992-4ee0-b420-90b86c5464a1@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