From: Bjorn Helgaas <helgaas@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Feng Tang" <feng.tang@linux.alibaba.com>,
"Jonathan Cameron" <Jonthan.Cameron@huawei.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/6] PCI/portdrv: Use bus-type functions
Date: Tue, 13 Jan 2026 15:50:15 -0600 [thread overview]
Message-ID: <20260113215015.GA781767@bhelgaas> (raw)
In-Reply-To: <cover.1764688034.git.u.kleine-koenig@baylibre.com>
On Tue, Dec 02, 2025 at 04:13:48PM +0100, Uwe Kleine-König wrote:
> Hello,
>
> with the eventual goal to remore .probe(), .remove() and .shutdown()
> from struct device_driver convert pcie portdrv to use bus-type
> callbacks.
>
> The first patch is a fix, but I think it's not relevant as I didn't find
> a pcie driver without a remove callback. Feel free to drop the Fixes
> line if you think it's not justified and decide yourself if you want it
> backported to stable. I have no strong opinion here.
>
> For the complete series there is no intended change in behaviour (apart
> from the fix in the first patch :-).
>
> Best regards
> Uwe
>
> Uwe Kleine-König (6):
> PCI/portdrv: Fix potential resource leak
> PCI/portdrv: Drop empty shutdown callback
> PCI/portdrv: Don't check for the driver's and device's bus
> PCI/portdrv: Move pcie_port_bus_type to pcie source file
> PCI/portdrv: Don't check for valid device and driver in bus callbacks
> PCI/portdrv: Use bus-type functions
>
> drivers/pci/pci-driver.c | 28 -------------------
> drivers/pci/pcie/portdrv.c | 55 +++++++++++++++++++-------------------
> 2 files changed, 28 insertions(+), 55 deletions(-)
Applied to pci/portdrv for v6.20, thanks for doing this!
prev parent reply other threads:[~2026-01-13 21:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 15:13 [PATCH 0/6] PCI/portdrv: Use bus-type functions Uwe Kleine-König
2025-12-02 15:13 ` [PATCH 1/6] PCI/portdrv: Fix potential resource leak Uwe Kleine-König
2025-12-11 17:19 ` Ilpo Järvinen
2025-12-19 12:07 ` Jonathan Cameron
2025-12-02 15:13 ` [PATCH 2/6] PCI/portdrv: Drop empty shutdown callback Uwe Kleine-König
2025-12-02 16:10 ` Uwe Kleine-König
2025-12-11 17:20 ` Ilpo Järvinen
2025-12-19 12:08 ` Jonathan Cameron
2025-12-02 15:13 ` [PATCH 3/6] PCI/portdrv: Don't check for the driver's and device's bus Uwe Kleine-König
2025-12-19 12:11 ` Jonathan Cameron
2025-12-02 15:13 ` [PATCH 4/6] PCI/portdrv: Move pcie_port_bus_type to pcie source file Uwe Kleine-König
2025-12-11 17:28 ` Ilpo Järvinen
2025-12-12 22:35 ` Uwe Kleine-König
2026-01-12 10:43 ` Uwe Kleine-König
2025-12-02 15:13 ` [PATCH 5/6] PCI/portdrv: Don't check for valid device and driver in bus callbacks Uwe Kleine-König
2025-12-19 12:12 ` Jonathan Cameron
2025-12-02 15:13 ` [PATCH 6/6] PCI/portdrv: Use bus-type functions Uwe Kleine-König
2025-12-19 12:13 ` Jonathan Cameron
2026-01-13 21:50 ` 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=20260113215015.GA781767@bhelgaas \
--to=helgaas@kernel.org \
--cc=Jonthan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=u.kleine-koenig@baylibre.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