From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Upadhyay, Tejas" <tejas.upadhyay@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/ptl: Add missing device ID
Date: Wed, 11 Dec 2024 13:55:40 -0500 [thread overview]
Message-ID: <Z1ngLDwUKbl_6rwO@intel.com> (raw)
In-Reply-To: <SJ1PR11MB620402597212EED8751116A3813E2@SJ1PR11MB6204.namprd11.prod.outlook.com>
On Wed, Dec 11, 2024 at 01:52:37PM -0500, Upadhyay, Tejas wrote:
>
>
> > -----Original Message-----
> > From: Vivi, Rodrigo <rodrigo.vivi@intel.com>
> > Sent: Wednesday, December 11, 2024 11:47 PM
> > To: Upadhyay, Tejas <tejas.upadhyay@intel.com>
> > Cc: intel-xe@lists.freedesktop.org
> > Subject: Re: [PATCH] drm/xe/ptl: Add missing device ID
> >
> > On Wed, Dec 11, 2024 at 07:43:06PM +0530, Tejas Upadhyay wrote:
> > > Probably during movement from xe_pciids.h to pciids.h PTL device id is
> > missed.
> >
> > Please check if this is indeed true and if true add this with certainty and with
> > a Fixes tag. Otherwise keep the message simply as 'Add a missing PCI ID' or
> > 'Add a new PTL PCI ID'. Always imperative mode.
>
> Yes for sure its missed. We used to have this PCIID in xe_pciids.h.
>
> However, I just found out, drm-tip has this PCIID so probably some next backmerges will take care of this. Please, lets drop this patch.
Indeed:
ae78ec0a52c4 ("drm/xe/ptl: Add another PTL PCI ID")
drm-xe-next
CommitDate: Fri Nov 22 13:58:13 2024 -0800
>
> Tejas
>
> >
> > >
> > > Signed-off-by: Tejas Upadhyay <tejas.upadhyay@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.34.1
> > >
next prev parent reply other threads:[~2024-12-11 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 14:13 [PATCH] drm/xe/ptl: Add missing device ID Tejas Upadhyay
2024-12-11 14:26 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-12-11 18:17 ` [PATCH] " Rodrigo Vivi
2024-12-11 18:52 ` Upadhyay, Tejas
2024-12-11 18:55 ` Rodrigo Vivi [this message]
2024-12-11 18:54 ` Saarinen, Jani
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=Z1ngLDwUKbl_6rwO@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tejas.upadhyay@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