From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: "Surendrakumar Upadhyay,
TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Add RPL-S PCI IDs
Date: Mon, 28 Mar 2022 09:29:51 +0000 [thread overview]
Message-ID: <63d4a04fb3fd418ab026761eb36bba6e@intel.com> (raw)
In-Reply-To: <PH7PR11MB581969EAC14DC035B37E4046DF1D9@PH7PR11MB5819.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of
> Surendrakumar Upadhyay, TejaskumarX
> Sent: Monday, March 28, 2022 2:52 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] drm/i915: Add RPL-S PCI IDs
>
> Gentle reminder to review below change.
>
> Thanks,
> Tejas
>
> > -----Original Message-----
> > From: Surendrakumar Upadhyay, TejaskumarX
> > Sent: 25 March 2022 12:17
> > To: intel-gfx@lists.freedesktop.org
> > Cc: Roper, Matthew D <matthew.d.roper@intel.com>; Meena, Mahesh
> > <Mahesh.Meena@intel.com>
> > Subject: RE: [PATCH] drm/i915: Add RPL-S PCI IDs
> >
> > Can anyone please give review on this?
> >
> > Thanks,
> > Tejas
> >
> > > -----Original Message-----
> > > From: Surendrakumar Upadhyay, TejaskumarX
> > > <tejaskumarx.surendrakumar.upadhyay@intel.com>
> > > Sent: 22 March 2022 09:36
> > > To: intel-gfx@lists.freedesktop.org
> > > Cc: Surendrakumar Upadhyay, TejaskumarX
> > > <tejaskumarx.surendrakumar.upadhyay@intel.com>; Roper, Matthew D
> > > <matthew.d.roper@intel.com>
> > > Subject: [PATCH] drm/i915: Add RPL-S PCI IDs
> > >
> > > Add couple of RPL-S device ids
> > >
> > > Bspec : 53655
> > > Cc: Matt Roper <matthew.d.roper@intel.com>
> > > Signed-off-by: Tejas Upadhyay
> > > <tejaskumarx.surendrakumar.upadhyay@intel.com>
LGTM.
Reviewed-by: Anshuman Gupta <anshuman.gupta@intel.com>
> > > ---
> > > include/drm/i915_pciids.h | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> > > index
> > > 3609f3254f24..638be9cddba4 100644
> > > --- a/include/drm/i915_pciids.h
> > > +++ b/include/drm/i915_pciids.h
> > > @@ -679,7 +679,9 @@
> > > INTEL_VGA_DEVICE(0xA782, info), \
> > > INTEL_VGA_DEVICE(0xA783, info), \
> > > INTEL_VGA_DEVICE(0xA788, info), \
> > > - INTEL_VGA_DEVICE(0xA789, info)
> > > + INTEL_VGA_DEVICE(0xA789, info), \
> > > + INTEL_VGA_DEVICE(0xA78A, info), \
> > > + INTEL_VGA_DEVICE(0xA78B, info)
> > >
> > > /* DG2 */
> > > #define INTEL_DG2_G10_IDS(info) \
> > > --
> > > 2.34.1
next prev parent reply other threads:[~2022-03-28 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 4:06 [Intel-gfx] [PATCH] drm/i915: Add RPL-S PCI IDs Tejas Upadhyay
2022-03-22 4:40 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2022-03-22 5:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-22 16:14 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-03-25 6:46 ` [Intel-gfx] [PATCH] " Surendrakumar Upadhyay, TejaskumarX
2022-03-28 9:21 ` Surendrakumar Upadhyay, TejaskumarX
2022-03-28 9:29 ` Gupta, Anshuman [this message]
2022-03-29 14:57 ` Matt Roper
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=63d4a04fb3fd418ab026761eb36bba6e@intel.com \
--to=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tejaskumarx.surendrakumar.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