From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Bjorn Helgaas <bhelgaas@google.com>,
Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
linux-pci@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] PCI+IB/hfi1: Fold duplicate secondary bus reset code
Date: Tue, 5 May 2026 01:03:34 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2605050042390.46195@angie.orcam.me.uk> (raw)
Hi,
This v2 of the patch series addresses a documentation issue raised in v1.
In the course of verifying my PCIe link training failure workaround (cf.
<https://lore.kernel.org/r/alpine.DEB.2.21.2305310024400.59226@angie.orcam.me.uk/>)
in the context of secondary bus reset handling I found a piece of code in
the InfiniBand HFI1 driver that duplicates what we already have as private
code in PCI core. This patch series removes this duplication by exporting
said private code and than making use of it in the HFI1 driver.
As I have no means to run-time verify InfiniBand code I have only build
these patches, for x86-64, with the HFI1 driver both built in and modular.
Please see individual change descriptions for further details.
Please consider.
Previous iterations:
- v1 at: <https://lore.kernel.org/r/alpine.DEB.2.21.2306200153110.14084@angie.orcam.me.uk/>.
Maciej
next reply other threads:[~2026-05-05 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 0:03 Maciej W. Rozycki [this message]
2026-05-05 0:03 ` [PATCH v2 1/2] PCI: Export pci_parent_bus_reset() for drivers to use Maciej W. Rozycki
2026-05-05 0:38 ` sashiko-bot
2026-05-12 9:00 ` Leon Romanovsky
2026-05-12 10:17 ` Maciej W. Rozycki
2026-05-14 15:39 ` Leon Romanovsky
2026-05-14 16:29 ` Dennis Dalessandro
2026-05-16 0:47 ` Maciej W. Rozycki
2026-05-05 0:03 ` [PATCH v2 2/2] IB/hfi1: Remove pci_parent_bus_reset() duplication Maciej W. Rozycki
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=alpine.DEB.2.21.2605050042390.46195@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=bhelgaas@google.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).