From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <kbusch@meta.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com, lukas@wunner.de,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv3 0/5] pci cleanup/prep patches
Date: Wed, 23 Oct 2024 17:20:30 -0500 [thread overview]
Message-ID: <20241023222030.GA941303@bhelgaas> (raw)
In-Reply-To: <20241022224851.340648-1-kbusch@meta.com>
On Tue, Oct 22, 2024 at 03:48:46PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> This is a subset of a previous RFC bus lock patches that are simply good
> cleanups that should help make it easier to introduce different locking
> later.
>
> Changes from v2:
>
> Rebased to pci/next
>
> Added memory barriers around bit ops for patch 1.
>
> Added reviews.
>
> Keith Busch (5):
> pci: make pci_stop_dev concurrent safe
> pci: make pci_destroy_dev concurrent safe
> pci: move the walk bus lock to where its needed
> pci: walk bus recursively
> pci: unexport pci_walk_bus_locked
>
> drivers/pci/bus.c | 49 +++++++++++++++-----------------------------
> drivers/pci/pci.h | 17 +++++++++++++--
> drivers/pci/remove.c | 22 +++++++++-----------
> 3 files changed, 41 insertions(+), 47 deletions(-)
Applied to pci/locking for v6.13, thanks Keith!
prev parent reply other threads:[~2024-10-23 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 22:48 [PATCHv3 0/5] pci cleanup/prep patches Keith Busch
2024-10-22 22:48 ` [PATCHv3 1/5] pci: make pci_stop_dev concurrent safe Keith Busch
2024-11-07 14:06 ` Lukas Wunner
2024-11-07 15:56 ` Keith Busch
2024-11-11 7:20 ` Lukas Wunner
2024-10-22 22:48 ` [PATCHv3 2/5] pci: make pci_destroy_dev " Keith Busch
2024-10-22 22:48 ` [PATCHv3 3/5] pci: move the walk bus lock to where its needed Keith Busch
2024-10-22 22:48 ` [PATCHv3 4/5] pci: walk bus recursively Keith Busch
2024-11-11 8:21 ` Lukas Wunner
2024-10-22 22:48 ` [PATCHv3 5/5] pci: unexport pci_walk_bus_locked Keith Busch
2024-10-23 21:43 ` Bjorn Helgaas
2024-10-23 22:00 ` Keith Busch
2024-10-23 22:07 ` Bjorn Helgaas
2024-10-23 22:20 ` Bjorn Helgaas [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=20241023222030.GA941303@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.