From: Hans Zhang <18255117159@163.com>
To: mahesh@linux.ibm.com, bhelgaas@google.com
Cc: oohall@gmail.com, mani@kernel.org, lukas@wunner.de,
linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v4 0/2] PCI: Introduce pci_clear/set_config_dword()
Date: Sun, 18 Jan 2026 21:47:54 +0800 [thread overview]
Message-ID: <1d267e9e-5e32-483c-8b53-1454d4dc5e9a@163.com> (raw)
In-Reply-To: <20251101162219.12016-1-18255117159@163.com>
Hi,
Gentle ping.
Best regards,
Hans
On 2025/11/2 00:22, Hans Zhang wrote:
> This series introduces auxiliary functions for the PCI configuration space
> and simplifies the read and write operations of the AER driver, reducing a
> lot of repetitive code.
>
> Patch 1 adds pci_clear_config_dword() and pci_set_config_dword() helpers
> to reduce repetitive read-modify-write sequences when modifying PCI config
> space. These helpers improve code readability and maintainability.
>
> Patch 2 refactors the PCIe AER driver to use these new helpers,
> eliminating manual read-modify-write patterns and intermediate variable
> in several functions. This results in cleaner and more concise code.
>
> ---
> Changes for v4:
> - Introduce pci_clear/set_config_dword()
>
> Changes for v3:
> https://patchwork.kernel.org/project/linux-pci/patch/20250816161743.340684-1-18255117159@163.com/
>
> - Rebase to v6.17-rc1.
> - The patch commit message were modified.
> - Add Acked-by: Manivannan Sadhasivam <mani@kernel.org>
>
> Changes for v2:
> - The patch commit message were modified.
> - New optimizations for the functions disable_ecrc_checking, aer_enable_irq, and aer_disable_irq have been added.
> ---
>
> Hans Zhang (2):
> PCI: Introduce pci_clear/set_config_dword()
> PCI/AER: Use pci_clear/set_config_dword to simplify code
>
> drivers/pci/pcie/aer.c | 29 ++++++++++-------------------
> include/linux/pci.h | 12 ++++++++++++
> 2 files changed, 22 insertions(+), 19 deletions(-)
>
>
> base-commit: 8742b2d8935f476449ef37e263bc4da3295c7b58
next prev parent reply other threads:[~2026-01-18 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 16:22 [RESEND PATCH v4 0/2] PCI: Introduce pci_clear/set_config_dword() Hans Zhang
2025-11-01 16:22 ` [RESEND PATCH v4 1/2] " Hans Zhang
2025-11-01 16:22 ` [RESEND PATCH v4 2/2] PCI/AER: Use pci_clear/set_config_dword to simplify code Hans Zhang
2026-01-18 13:47 ` Hans Zhang [this message]
2026-03-06 15:50 ` [RESEND PATCH v4 0/2] PCI: Introduce pci_clear/set_config_dword() Hans Zhang
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=1d267e9e-5e32-483c-8b53-1454d4dc5e9a@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=mahesh@linux.ibm.com \
--cc=mani@kernel.org \
--cc=oohall@gmail.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