From: "Gupta, Varun" <varun.gupta@intel.com>
To: <himanshu.girotra@intel.com>, <ramadevi.gandi@intel.com>,
<aditya.chauhan@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] lib/pciids: sync with kernel commit e68a60f9e6a6
Date: Mon, 11 May 2026 10:45:05 +0530 [thread overview]
Message-ID: <43a40a9a-7571-4257-bd1b-0ccf45d98d92@intel.com> (raw)
In-Reply-To: <20260511045955.23541-1-himanshu.girotra@intel.com>
Hi,
On 11-May-26 10:29 AM, himanshu.girotra@intel.com wrote:
> From: Himanshu Girotra <himanshu.girotra@intel.com>
>
> Synchronize PCI IDs with drm-next kernel up to e68a60f9e6a6,
> which includes the following changes:
>
> commit e68a60f9e6a6 ("drm/xe/cri: Add new PCI IDs")
>
> Signed-off-by: Himanshu Girotra <himanshu.girotra@intel.com>
> ---
> lib/pciids.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/lib/pciids.h b/lib/pciids.h
> index 33b91cb2e..e32ef7634 100644
> --- a/lib/pciids.h
> +++ b/lib/pciids.h
> @@ -898,7 +898,11 @@
>
> /* CRI */
> #define INTEL_CRI_IDS(MACRO__, ...) \
> - MACRO__(0x674C, ## __VA_ARGS__)
> + MACRO__(0x674C, ## __VA_ARGS__), \
> + MACRO__(0x674D, ## __VA_ARGS__), \
> + MACRO__(0x674E, ## __VA_ARGS__), \
> + MACRO__(0x674F, ## __VA_ARGS__), \
> + MACRO__(0x6750, ## __VA_ARGS__)
>
> /* NVL-P */
> #define INTEL_NVLP_IDS(MACRO__, ...) \
LGTM,
Reviewed-by: Varun Gupta <varun.gupta@intel.com>
next prev parent reply other threads:[~2026-05-11 5:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 4:59 [PATCH i-g-t] lib/pciids: sync with kernel commit e68a60f9e6a6 himanshu.girotra
2026-05-11 5:15 ` Gupta, Varun [this message]
2026-05-11 23:02 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-05-11 23:08 ` ✓ i915.CI.BAT: " Patchwork
2026-05-12 7:59 ` ✗ i915.CI.Full: failure " Patchwork
2026-05-13 5:08 ` ✗ Xe.CI.FULL: " Patchwork
2026-05-13 5:21 ` Girotra, Himanshu
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=43a40a9a-7571-4257-bd1b-0ccf45d98d92@intel.com \
--to=varun.gupta@intel.com \
--cc=aditya.chauhan@intel.com \
--cc=himanshu.girotra@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ramadevi.gandi@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