From: Bjorn Helgaas <helgaas@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] x86/pci: consolidate x86-specific PCI quirks into arch/x86/pci/fixup.c
Date: Fri, 10 Jul 2026 15:46:50 -0500 [thread overview]
Message-ID: <20260710204650.GA998073@bhelgaas> (raw)
In-Reply-To: <20260707221800.920270-1-rosenp@gmail.com>
On Tue, Jul 07, 2026 at 03:17:52PM -0700, Rosen Penev wrote:
> This series moves all x86-specific PCI quirks from the generic
> drivers/pci/quirks.c into arch/x86/pci/fixup.c, where they
> architecturally belong. This reduces the ifdef burden in the generic
> quirk file and improves build granularity by gating the x86 fixups
> behind CONFIG_PCI_QUIRKS.
>
> The series is organized as a preparatory commit followed by one
> commit per vendor/family, keeping each move reviewable.
>
> Suggested by: https://lore.kernel.org/all/20161221142607.GA8594@infradead.org/
>
> Rosen Penev (8):
> x86/pci: gate arch fixups with CONFIG_PCI_QUIRKS
> x86/pci: move Intel chipset quirks to arch/x86/pci/fixup.c
> x86/pci: move VIA chipset quirks to arch/x86/pci/fixup.c
> x86/pci: move SiS chipset quirks to arch/x86/pci/fixup.c
> x86/pci: move ALi chipset quirks to arch/x86/pci/fixup.c
> x86/pci: move AMD x86 chipset quirks to arch/x86/pci/fixup.c
> x86/pci: move x86 ifdef-gated quirks to arch/x86/pci/fixup.c
> x86/pci: move remaining x86-specific quirks to fixup.c
>
> arch/x86/pci/Makefile | 2 +-
> arch/x86/pci/fixup.c | 2284 ++++++++++++++++++++++++++++++++++++++++
> drivers/pci/pci.h | 3 +
> drivers/pci/quirks.c | 2330 +----------------------------------------
> 4 files changed, 2316 insertions(+), 2303 deletions(-)
I don't object to any of this from a PCI perspective, so I guess it's
up to the x86 folks if they want them.
It looks like the typical subject line style in fixup.c is:
x86/PCI: <Capitalized-first-word> ...
next prev parent reply other threads:[~2026-07-10 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 22:17 [PATCH 0/8] x86/pci: consolidate x86-specific PCI quirks into arch/x86/pci/fixup.c Rosen Penev
2026-07-07 22:17 ` [PATCH 1/8] x86/pci: gate arch fixups with CONFIG_PCI_QUIRKS Rosen Penev
2026-07-07 22:17 ` [PATCH 2/8] x86/pci: move Intel chipset quirks to arch/x86/pci/fixup.c Rosen Penev
2026-07-07 22:17 ` [PATCH 3/8] x86/pci: move VIA " Rosen Penev
2026-07-07 22:17 ` [PATCH 4/8] x86/pci: move SiS " Rosen Penev
2026-07-07 22:17 ` [PATCH 5/8] x86/pci: move ALi " Rosen Penev
2026-07-07 22:17 ` [PATCH 6/8] x86/pci: move AMD x86 " Rosen Penev
2026-07-07 22:17 ` [PATCH 7/8] x86/pci: move x86 ifdef-gated " Rosen Penev
2026-07-07 22:18 ` [PATCH 8/8] x86/pci: move remaining x86-specific quirks to fixup.c Rosen Penev
2026-07-10 20:46 ` Bjorn Helgaas [this message]
2026-07-10 20:51 ` [PATCH 0/8] x86/pci: consolidate x86-specific PCI quirks into arch/x86/pci/fixup.c Rosen Penev
2026-07-10 21:27 ` Bjorn Helgaas
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=20260710204650.GA998073@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rosenp@gmail.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/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