From: Bjorn Helgaas <helgaas@kernel.org>
To: Hans Zhang <18255117159@163.com>
Cc: bhelgaas@google.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, jingoohan1@gmail.com,
robh@kernel.org, s32@nxp.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 00/16] PCI: Use FIELD_MODIFY() to simplify bitfield operations
Date: Tue, 5 May 2026 11:54:36 -0500 [thread overview]
Message-ID: <20260505165436.GA737933@bhelgaas> (raw)
In-Reply-To: <20260430162420.42839-1-18255117159@163.com>
On Fri, May 01, 2026 at 12:24:04AM +0800, Hans Zhang wrote:
> Replace open-coded bitmask clear + FIELD_PREP() sequences with the
> dedicated FIELD_MODIFY() macro. FIELD_MODIFY() performs the same
> operation but is shorter, less error-prone, and includes compile-time
> checks to prevent field overflow.
>
> This series touches the PCI core, PCIe extended capabilities (PTM, IDE,
> TPH, MSI, REBAR, IOV, CardBus), and several DesignWare-based and
> other PCI host controllers. No functional change is intended.
>
> The patches are split per subsystem or per driver to ease review:
> ---
> Hi, If the Maintainers think it's not necessary, please ignore it.
> ---
>
> Hans Zhang (16):
> PCI: Use FIELD_MODIFY()
> PCI/PTM: Use FIELD_MODIFY()
> PCI/IDE: Use FIELD_MODIFY()
> PCI/IOV: Use FIELD_MODIFY()
> PCI/TPH: Use FIELD_MODIFY()
> PCI/MSI: Use FIELD_MODIFY()
> PCI/REBAR: Use FIELD_MODIFY()
> PCI/CARDBUS: Use FIELD_MODIFY()
> PCI: al: Use FIELD_MODIFY()
> PCI: eswin: Use FIELD_MODIFY()
> PCI: s32g: Use FIELD_MODIFY()
> PCI: tegra194: Use FIELD_MODIFY()
> PCI: qcom: Use FIELD_MODIFY()
> PCI: dwc: Use FIELD_MODIFY()
> PCI: mvebu: Use FIELD_MODIFY()
> PCI: mediatek-gen3: Use FIELD_MODIFY()
>
> drivers/pci/controller/dwc/pcie-al.c | 12 ++----
> .../controller/dwc/pcie-designware-debugfs.c | 23 ++++-------
> .../pci/controller/dwc/pcie-designware-ep.c | 3 +-
> drivers/pci/controller/dwc/pcie-designware.c | 3 +-
> drivers/pci/controller/dwc/pcie-eswin.c | 3 +-
> drivers/pci/controller/dwc/pcie-nxp-s32g.c | 3 +-
> drivers/pci/controller/dwc/pcie-qcom-common.c | 40 +++++++------------
> drivers/pci/controller/dwc/pcie-qcom-ep.c | 6 +--
> drivers/pci/controller/dwc/pcie-tegra194.c | 8 ++--
> drivers/pci/controller/pci-mvebu.c | 3 +-
> drivers/pci/controller/pcie-mediatek-gen3.c | 3 +-
> drivers/pci/ide.c | 6 +--
> drivers/pci/iov.c | 3 +-
> drivers/pci/msi/msi.c | 11 ++---
> drivers/pci/pci.c | 3 +-
> drivers/pci/pcie/ptm.c | 3 +-
> drivers/pci/rebar.c | 6 +--
> drivers/pci/setup-cardbus.c | 3 +-
> drivers/pci/tph.c | 10 ++---
> 19 files changed, 51 insertions(+), 101 deletions(-)
I squashed these together since they're all doing exactly the same
thing and applied to pci/misc for v7.2, thanks! I think this makes it
noticeably easier to read, especially in the cases where we update
several register fields at once.
Sashiko noticed the dev->sriov->barsz[] array bounds issue, which is
mostly addressed by another pending patch: https://patch.msgid.link/44a4ae53ec2825816b816c85cd378430d9a95cc6.1776429882.git.mnencia@kcore.it
Sashiko also flagged a potential pcie-mediatek-gen3.c issue related to
checking the return from pci_runtime_get_sync(), but that has nothing
to do with this patch, so I'll just forward that to the Mediatek
folks.
https://sashiko.dev/#/patchset/20260430162420.42839-1-18255117159%40163.com
prev parent reply other threads:[~2026-05-05 16:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 16:24 [RESEND PATCH 00/16] PCI: Use FIELD_MODIFY() to simplify bitfield operations Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 01/16] PCI: Use FIELD_MODIFY() Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 02/16] PCI/PTM: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 03/16] PCI/IDE: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 04/16] PCI/IOV: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 05/16] PCI/TPH: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 06/16] PCI/MSI: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 07/16] PCI/REBAR: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 08/16] PCI/CARDBUS: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 09/16] PCI: al: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 10/16] PCI: eswin: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 11/16] PCI: s32g: " Hans Zhang
2026-05-04 19:12 ` Frank Li
2026-04-30 16:24 ` [RESEND PATCH 12/16] PCI: tegra194: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 13/16] PCI: qcom: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 14/16] PCI: dwc: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 15/16] PCI: mvebu: " Hans Zhang
2026-04-30 16:24 ` [RESEND PATCH 16/16] PCI: mediatek-gen3: " Hans Zhang
2026-04-30 18:08 ` [RESEND PATCH 00/16] PCI: Use FIELD_MODIFY() to simplify bitfield operations Bjorn Helgaas
2026-05-01 14:19 ` Hans Zhang
2026-05-05 16:54 ` Bjorn Helgaas [this message]
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=20260505165436.GA737933@bhelgaas \
--to=helgaas@kernel.org \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=s32@nxp.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