Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: bhelgaas@google.com, lpieralisi@kernel.org,
	kwilczynski@kernel.org, mani@kernel.org, jingoohan1@gmail.com
Cc: robh@kernel.org, s32@nxp.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/16] PCI: Use FIELD_MODIFY() to simplify bitfield operations
Date: Fri, 1 May 2026 00:22:07 +0800	[thread overview]
Message-ID: <336f827e-71da-49af-be9b-6f555cd3cbb1@163.com> (raw)
In-Reply-To: <20260430161254.40278-1-18255117159@163.com>


Sorry for the noise.Due to my current system issues, the remaining 
patches were not sent out. I will resend them now.

Hans

On 5/1/26 00:12, 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(-)
> 
> 
> base-commit: 3b3bea6d4b9c162f9e555905d96b8c1da67ecd5b


      parent reply	other threads:[~2026-04-30 16:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 16:12 [PATCH 00/16] PCI: Use FIELD_MODIFY() to simplify bitfield operations Hans Zhang
2026-04-30 16:12 ` [PATCH 01/16] PCI: Use FIELD_MODIFY() Hans Zhang
2026-04-30 16:12 ` [PATCH 02/16] PCI/PTM: " Hans Zhang
2026-04-30 16:12 ` [PATCH 03/16] PCI/IDE: " Hans Zhang
2026-04-30 16:12 ` [PATCH 04/16] PCI/IOV: " Hans Zhang
2026-04-30 16:12 ` [PATCH 05/16] PCI/TPH: " Hans Zhang
2026-04-30 16:12 ` [PATCH 06/16] PCI/MSI: " Hans Zhang
2026-04-30 16:12 ` [PATCH 07/16] PCI/REBAR: " Hans Zhang
2026-04-30 16:12 ` [PATCH 08/16] PCI/CARDBUS: " Hans Zhang
2026-04-30 16:12 ` [PATCH 09/16] PCI: al: " Hans Zhang
2026-04-30 16:12 ` [PATCH 10/16] PCI: eswin: " Hans Zhang
2026-04-30 16:22 ` Hans Zhang [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=336f827e-71da-49af-be9b-6f555cd3cbb1@163.com \
    --to=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