On Mon May 18, 2026 at 9:31 PM CEST, David Jeffery wrote: > These patches are now rebased against the driver-core tree's driver-core-next > branch.
[...] > Changes from V15: > > The async_shutdown bit field is converted to a device flags bit Convert all > patches to use the flag bit accessor macros to set or check if async shutdown > should be used Added documentation on the kernel parameter to control use of > async shutdown Did you have a look at the Sashiko report from v15 [1]? Some of the concerns raised seem valid at a quick glance. (It seems that this version has not been picked up by Sashiko (despite you mentioning they are based on driver-core-next). I'd assume it doesn't like that the series was not sent with '--base'.) Can you have a look at [1] please? Thanks, Danilo [1] https://sashiko.dev/#/patchset/20260429175016.7915-1-djeffery%40redhat.com > Stuart Hayes (2): > driver core: separate function to shutdown one device > driver core: do not always lock parent in shutdown > > David Jeffery (3): > driver core: async device shutdown infrastructure > PCI: Enable async shutdown support > scsi: Enable async shutdown support Not sure it will make it for 7.2, but I think it would be good to give this some more time in linux-next anyways. Bjorn, James, Martin: Should the PCI and scsi patch go through the driver-core tree too? Do you prefer a signed tag with the driver-core changes to merge into the PCI and scsi trees?
