[PATCH 4/5] PCI: Enable async shutdown support

[Bjorn Helgaas]

On Wed, May 06, 2026 at 05:10:19PM -0400, David Jeffery wrote:
> On Wed, May 6, 2026 at 2:28 PM Bjorn Helgaas <helgaas at kernel.org> wrote:
> > On Wed, Apr 29, 2026 at 01:50:15PM -0400, David Jeffery wrote:
> > > Like its async suspend support, allow PCI device shutdown to be performed
> > > asynchronously to reduce shutdown time.
> > >
> > > Signed-off-by: David Jeffery <djeffery at redhat.com>
> > > Signed-off-by: Stuart Hayes <stuart.w.hayes at gmail.com>
> > > Tested-by: Laurence Oberman <loberman at redhat.com>
> > > Reviewed-by: Martin K. Petersen <martin.petersen at oracle.com>
> > > Reviewed-by: Pasha Tatashin <pasha.tatashin at soleen.com>
> >
> > Reviewed-by: Bjorn Helgaas <bhelgaas at google.com>
> >
> > I'm concerned about tripping over driver issues, but it's a pretty big
> > benefit.  I think it's worth mentioning the "async_shutdown" module
> > parameter somewhere in the commit logs and putting an example in
> > Documentation/admin-guide/kernel-parameters.txt.
> 
> Sure, I can see about adding a document patch to it.
> 
> > Might even consider keeping in -next for a cycle+ and targeting v7.3.
> 
> I would be happy for it to spend as much time in linux-next as needed
> for people to be comfortable with the risk of odd interactions with
> all the pci drivers it will indirectly impact.
> 
> But I must admit my ignorance with some of the details of linux-next.
> Looking at the main code changes, the patchset would seem to want to
> go through driver-core to get to linux-next. But as far as indirect
> impact, it is the diverse collection of devices and drivers under PCI
> which are most affected by the changes. Is there a consensus on how to
> steward a patchset like this one into linux-next?

My guess is it should all go via the driver-core tree, given acks or
reviewed-by from the other subsystems it touches.