From: sashiko-bot@kernel.org
To: "Pavel Popov" <pavel.e.popov@intel.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 2/7] drm/i915: Include <asm/cpu_device_id.h> unconditionally
Date: Thu, 12 Nov 2026 00:17:19 +0000 [thread overview]
Message-ID: <sashiko-outbox-209896@kernel.org> (raw)
In-Reply-To: <20261111234821.4814-3-pavel.e.popov@intel.com>
> <asm/cpu_device_id.h> now has a generic version, so the #ifdef
> CONFIG_X86 around the include is no longer needed.
>
> <asm/intel-family.h> is included by <asm/cpu_device_id.h>. The CPU
> match table still needs CONFIG_X86 for the INTEL_* model defines.
>
> Signed-off-by: Pavel Popov <pavel.e.popov@intel.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111234821.4814-1-pavel.e.popov@intel.com?part=2
next prev parent reply other threads:[~2026-11-12 0:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 23:48 [PATCH 0/7] Include <asm/cpu_device_id.h> without #ifdef CONFIG_X86 Pavel Popov
2026-11-11 23:48 ` [PATCH 1/7] ACPI: mipi-disco-img: Include <asm/cpu_device_id.h> unconditionally Pavel Popov
2026-11-12 0:15 ` sashiko-bot
2026-11-11 23:48 ` [PATCH 2/7] drm/i915: " Pavel Popov
2026-11-12 0:17 ` sashiko-bot [this message]
2026-11-12 4:41 ` Raag Jadav
2026-11-11 23:48 ` [PATCH 3/7] drm/amdgpu: " Pavel Popov
2026-11-12 0:20 ` sashiko-bot
2026-11-11 23:48 ` [PATCH 4/7] cpufreq: ondemand: " Pavel Popov
2026-11-12 0:24 ` sashiko-bot
2026-11-12 3:22 ` Zhongqiu Han
2026-11-11 23:48 ` [PATCH 5/7] platform/x86: Include <asm/cpu_device_id.h> unconditionally in soc.h Pavel Popov
2026-11-12 0:27 ` sashiko-bot
2026-11-11 23:48 ` [PATCH 6/7] tpm: Include <asm/cpu_device_id.h> unconditionally Pavel Popov
2026-11-12 0:29 ` sashiko-bot
2026-11-12 0:40 ` Jarkko Sakkinen
2026-11-12 1:22 ` Popov, Pavel E
2026-11-11 23:48 ` [PATCH 7/7] crypto: ccp - Drop unused <asm/cpu_device_id.h> include Pavel Popov
2026-11-12 0:30 ` sashiko-bot
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=sashiko-outbox-209896@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pavel.e.popov@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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