From: "Danilo Krummrich" <dakr@kernel.org>
To: "David Jeffery" <djeffery@redhat.com>
Cc: linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Tarun Sahu" <tarunsahu@google.com>,
"Pasha Tatashin" <tatashin@google.com>,
"Michał Cłapiński" <mclapinski@google.com>,
"Jordan Richards" <jordanrichards@google.com>,
"Ewan Milne" <emilne@redhat.com>,
"John Meneghini" <jmeneghi@redhat.com>,
"Lombardi, Maurizio" <mlombard@redhat.com>,
"Stuart Hayes" <stuart.w.hayes@gmail.com>,
"Laurence Oberman" <loberman@redhat.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"John Garry" <john.g.garry@oracle.com>,
kexec@lists.infradead.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v16 0/5] shut down devices asynchronously
Date: Mon, 01 Jun 2026 17:09:59 +0200 [thread overview]
Message-ID: <DIXT3WV9XAWK.3E0JOPV2K6NC1@kernel.org> (raw)
In-Reply-To: <20260518193204.14273-1-djeffery@redhat.com>
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?
next prev parent reply other threads:[~2026-06-01 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 19:31 [PATCH v16 0/5] shut down devices asynchronously David Jeffery
2026-05-18 19:32 ` [PATCH 1/5] driver core: separate function to shutdown one device David Jeffery
2026-05-18 19:32 ` [PATCH 2/5] driver core: do not always lock parent in shutdown David Jeffery
2026-05-18 19:32 ` [PATCH 3/5] driver core: async device shutdown infrastructure David Jeffery
2026-05-18 19:32 ` [PATCH 4/5] PCI: Enable async shutdown support David Jeffery
2026-05-18 19:32 ` [PATCH 5/5] scsi: " David Jeffery
2026-06-01 15:09 ` Danilo Krummrich [this message]
2026-06-01 16:54 ` [PATCH v16 0/5] shut down devices asynchronously David Jeffery
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=DIXT3WV9XAWK.3E0JOPV2K6NC1@kernel.org \
--to=dakr@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=djeffery@redhat.com \
--cc=driver-core@lists.linux.dev \
--cc=emilne@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=jmeneghi@redhat.com \
--cc=john.g.garry@oracle.com \
--cc=jordanrichards@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=mclapinski@google.com \
--cc=mlombard@redhat.com \
--cc=rafael@kernel.org \
--cc=stuart.w.hayes@gmail.com \
--cc=tarunsahu@google.com \
--cc=tatashin@google.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