From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 03/10] lib: sync i915_pciids.h with kernel commit 7b43a37348b7
Date: Wed, 22 May 2024 12:09:34 -0400 [thread overview]
Message-ID: <Zk4YvleCltwEwvch@intel.com> (raw)
In-Reply-To: <819bd797a173eb001ce98deb3d9cd721d60d6eaf.1716373923.git.jani.nikula@intel.com>
On Wed, May 22, 2024 at 01:35:16PM +0300, Jani Nikula wrote:
> Synchronize i915_pciids.h with kernel commit:
>
> 7b43a37348b7 ("drm/i915/pciids: add INTEL_SNB_IDS()")
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> lib/i915_pciids.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/lib/i915_pciids.h b/lib/i915_pciids.h
> index 05f466ca8ce2..0d48c493dcce 100644
> --- a/lib/i915_pciids.h
> +++ b/lib/i915_pciids.h
> @@ -151,6 +151,10 @@
> INTEL_SNB_M_GT1_IDS(info), \
> INTEL_SNB_M_GT2_IDS(info)
>
> +#define INTEL_SNB_IDS(info) \
> + INTEL_SNB_D_IDS(info), \
> + INTEL_SNB_M_IDS(info)
> +
I thought we were missing the change in lib/intel_device_info.c,
but then I noticed they use 2 different structs for these platforms.
But a good thing to fully align the header itself
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> #define INTEL_IVB_M_GT1_IDS(info) \
> INTEL_VGA_DEVICE(0x0156, info) /* GT1 mobile */
>
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-05-22 16:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 10:35 [PATCH i-g-t 00/10] lib: sync i915_pciids.h and _local.h with kernel Jani Nikula
2024-05-22 10:35 ` [PATCH i-g-t 01/10] lib: sync i915_pciids.h with kernel commit 432ed92bfb55 Jani Nikula
2024-05-22 16:06 ` Rodrigo Vivi
2024-05-22 10:35 ` [PATCH i-g-t 02/10] lib: sync i915_pciids.h with kernel commit 41c0f8a36f15 Jani Nikula
2024-05-22 16:07 ` Rodrigo Vivi
2024-05-22 10:35 ` [PATCH i-g-t 03/10] lib: sync i915_pciids.h with kernel commit 7b43a37348b7 Jani Nikula
2024-05-22 16:09 ` Rodrigo Vivi [this message]
2024-05-22 10:35 ` [PATCH i-g-t 04/10] lib: sync i915_pciids.h with kernel commit 5c8c22adc802 Jani Nikula
2024-05-22 16:10 ` Rodrigo Vivi
2024-05-22 10:35 ` [PATCH i-g-t 05/10] lib: sync i915_pciids.h with kernel commit aa3d586e1624 Jani Nikula
2024-05-22 16:11 ` Rodrigo Vivi
2024-05-22 10:35 ` [PATCH i-g-t 06/10] lib: sync i915_pciids.h with kernel commit bfbda4722767 Jani Nikula
2024-05-22 16:11 ` Rodrigo Vivi
2024-05-22 10:35 ` [PATCH i-g-t 07/10] lib: sync i915_pciids.h with kernel commit 7858cc0b55e3 Jani Nikula
2024-05-22 16:12 ` Rodrigo Vivi
2024-05-22 10:35 ` [PATCH i-g-t 08/10] lib: sync i915_pciids.h with kernel commit d2c4b1db1c4f Jani Nikula
2024-05-22 16:13 ` Rodrigo Vivi
2024-05-22 10:35 ` [PATCH i-g-t 09/10] lib: sync i915_pciids.h with kernel commit cfa7772880f8 Jani Nikula
2024-05-22 16:19 ` Rodrigo Vivi
2024-05-22 10:35 ` [PATCH i-g-t 10/10] lib: switch i915_pciids_local.h to xe driver style PCI ID macros Jani Nikula
2024-05-22 16:21 ` Rodrigo Vivi
2024-05-22 17:13 ` Jani Nikula
2024-05-22 17:15 ` Rodrigo Vivi
2024-05-22 12:40 ` ✓ Fi.CI.BAT: success for lib: sync i915_pciids.h and _local.h with kernel Patchwork
2024-05-22 13:34 ` ✓ CI.xeBAT: " Patchwork
2024-05-22 17:22 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-23 14:10 ` Kamil Konieczny
2024-05-23 5:20 ` ✗ Fi.CI.IGT: " Patchwork
2024-05-23 14:11 ` Kamil Konieczny
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=Zk4YvleCltwEwvch@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@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