From: Hans Zhang <18255117159@163.com>
To: bhelgaas@google.com, mani@kernel.org, lpieralisi@kernel.org,
kwilczynski@kernel.org, thierry.reding@kernel.org,
ryder.lee@mediatek.com, jonathanh@nvidia.com
Cc: robh@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-tegra@vger.kernel.org, Hans Zhang <18255117159@163.com>
Subject: [PATCH v2 0/5] PCI: Encapsulate pcie_link_speed array access
Date: Sun, 8 Nov 2026 17:40:29 +0800 [thread overview]
Message-ID: <20261108094034.679945-1-18255117159@163.com> (raw)
Hi,
This series finishes encapsulating the pcie_link_speed[] array by
converting the remaining direct users to pcie_get_link_speed() and
making the array private to probe.c.
The pcie_get_link_speed() helper was introduced and accepted in the
v10 "PCI: of: Remove max-link-speed generation validation" series, but
a few users that were added later still index pcie_link_speed[]
directly.
Changes since v1:
- Rebase onto v7.4-rc1.
- Use pcie_get_link_speed(), which is already exported and
bounds-checked, instead of introducing a new to_pcie_link_speed()
helper.
- Split the pci.c change from the other core conversions, mirroring the
split between v1 patches 1 and 2.
- Convert probe.c's max_bus_speed lookup, which v1 missed.
- Convert the Tegra264 and MediaTek controller drivers, which were
added after the v10 series and would otherwise fail to build once the
array is no longer exported.
- Split the two controller conversions into separate patches so each
driver can be reviewed independently.
- Make pcie_link_speed[] static instead of only removing its extern
declaration and export.
v1 series: https://patchwork.kernel.org/project/linux-pci/patch/20260315160057.127639-1-18255117159@163.com/
Hans Zhang (5):
PCI: Use pcie_get_link_speed() in pci.c
PCI: Convert remaining core pcie_link_speed[] users
PCI: tegra264: Use pcie_get_link_speed()
PCI: mediatek: Use pcie_get_link_speed()
PCI: Make pcie_link_speed[] private to probe.c
drivers/pci/controller/pcie-mediatek.c | 2 +-
drivers/pci/controller/pcie-tegra264.c | 6 +++---
drivers/pci/pci-sysfs.c | 2 +-
drivers/pci/pci.c | 9 ++-------
drivers/pci/pci.h | 3 +--
drivers/pci/probe.c | 5 ++---
6 files changed, 10 insertions(+), 17 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.43.0
next reply other threads:[~2026-11-08 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 9:40 Hans Zhang [this message]
2026-11-08 9:40 ` [PATCH v2 1/5] PCI: Use pcie_get_link_speed() in pci.c Hans Zhang
2026-11-09 12:03 ` Ilpo Järvinen
2026-11-08 9:40 ` [PATCH v2 2/5] PCI: Convert remaining core pcie_link_speed[] users Hans Zhang
2026-11-08 9:40 ` [PATCH v2 3/5] PCI: tegra264: Use pcie_get_link_speed() Hans Zhang
2026-11-08 9:40 ` [PATCH v2 4/5] PCI: mediatek: " Hans Zhang
2026-11-08 9:40 ` [PATCH v2 5/5] PCI: Make pcie_link_speed[] private to probe.c 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=20261108094034.679945-1-18255117159@163.com \
--to=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®