public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: Bjorn Helgaas <helgaas@kernel.org>
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: Fri, 1 May 2026 22:19:31 +0800	[thread overview]
Message-ID: <92fa1579-9c00-4d60-a916-1d2af1fb63ef@163.com> (raw)
In-Reply-To: <20260430180857.GA421892@bhelgaas>



On 5/1/26 02:08, Bjorn Helgaas wrote:
> 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:
> 
> A "resend" implies that this is the same series as posted earlier but
> forgotten for some reason.  But the original was only twelve minutes
> earlier, and this adds more instances.  This should be a "v2" with a
> note about what changed from the original posting.  In any event, I'll
> ignore the original posting in favor of this one.


Hi Bjorn,

Sorry.

Due to the fact that my development environment uses the 163 email 
service provided by China, the command "git send-email 
--no-chain-reply-to --quiet --to xxx --cc xxx" will not send the patches 
if there are more than 10 of them. Therefore, the following command 
needs to be executed: git send-email --no-chain-reply-to --quiet 
--batch-size=5 --relogin-delay=10 --to xxx --cc xxx. This way, you can 
send more than 10 patches. Next time, I will be more careful when 
sending and will also increment the version number.

Best regards,
Hans

> 
> Looks like a good candidate for coccinelle.
> 
>> 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
>> -- 
>> 2.34.1
>>


  reply	other threads:[~2026-05-01 14:20 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 [this message]
2026-05-05 16:54 ` 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=92fa1579-9c00-4d60-a916-1d2af1fb63ef@163.com \
    --to=18255117159@163.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --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