Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Jordan Justen <jordan.l.justen@intel.com>
Cc: Matt Atwood <matthew.s.atwood@intel.com>,
	<intel-xe@lists.freedesktop.org>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/xe/ptl: Add another PTL PCI ID
Date: Fri, 22 Nov 2024 15:18:25 -0800	[thread overview]
Message-ID: <20241122230404.GH4891@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <173200808386.5661.16726110968459346849@jljusten-skl>

On Tue, Nov 19, 2024 at 01:21:23AM -0800, Jordan Justen wrote:
> I don't know what mechanism there is for dependencies, but based on my
> experience this patch should not be applied without "drm/xe/ptl:
> Update PTL GuC revision".
> 
> Ref: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32149
> 
> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>

Applied to drm-xe-next (and the referenced GuC patch has also already
landed earlier today).

Since drm-xe-next hasn't had a backmerge yet to pick up the conversion
of xe_pciids.h -> pciids.h I had to 'dim cat-to-fixup' to get the change
to stick around in pciids.h when drm-tip gets re-generated.  Although
the old xe_pciids.h header also seems to be coming back now and I
couldn't get the fixup patch to delete it properly.  Presumably that
will clear itself up whenever a backmerge happens, but +Cc Lucas FYI.


Matt

> 
> On 2024-11-14 15:44:10, Matt Atwood wrote:
> > An additional pci id has been added to bspec.
> > 
> > Bspec: 72574
> > Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
> > ---
> >  include/drm/intel/pciids.h | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/include/drm/intel/pciids.h b/include/drm/intel/pciids.h
> > index 32480b5563db..7883384acd5e 100644
> > --- a/include/drm/intel/pciids.h
> > +++ b/include/drm/intel/pciids.h
> > @@ -829,6 +829,7 @@
> >         MACRO__(0xB092, ## __VA_ARGS__), \
> >         MACRO__(0xB0A0, ## __VA_ARGS__), \
> >         MACRO__(0xB0A1, ## __VA_ARGS__), \
> > -       MACRO__(0xB0A2, ## __VA_ARGS__)
> > +       MACRO__(0xB0A2, ## __VA_ARGS__), \
> > +       MACRO__(0xB0B0, ## __VA_ARGS__)
> >  
> >  #endif /* __PCIIDS_H__ */
> > -- 
> > 2.45.0
> >

-- 
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation

  reply	other threads:[~2024-11-22 23:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 23:44 [PATCH] drm/xe/ptl: Add another PTL PCI ID Matt Atwood
2024-11-15  0:25 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-15  0:25 ` ✓ CI.checkpatch: " Patchwork
2024-11-15  0:26 ` ✓ CI.KUnit: " Patchwork
2024-11-15  0:38 ` ✓ CI.Build: " Patchwork
2024-11-15  0:40 ` ✓ CI.Hooks: " Patchwork
2024-11-15  0:41 ` ✗ CI.checksparse: warning " Patchwork
2024-11-15  1:10 ` ✓ CI.BAT: success " Patchwork
2024-11-15 18:48 ` ✗ CI.FULL: failure " Patchwork
2024-11-19  9:21 ` [PATCH] " Jordan Justen
2024-11-22 23:18   ` Matt Roper [this message]
2024-11-25  9:09     ` Jani Nikula

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=20241122230404.GH4891@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jordan.l.justen@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.s.atwood@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