From: sashiko-bot@kernel.org
To: driver-core@lists.linux.dev,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"David Jeffery" <djeffery@redhat.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
Maurizio <mlombard@redhat.com>,
kexec@lists.infradead.org, "Ewan Milne" <emilne@redhat.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"John Meneghini" <jmeneghi@redhat.com>,
linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org,
"Bjorn Helgaas" <bhelgaas@google.com>,
"John Garry" <john.g.garry@oracle.com>,
linux-kernel@vger.kernel.org,
"Bart Van Assche" <bvanassche@acm.org>,
"Tarun Sahu" <tarunsahu@google.com>,
"Jeremy Allison" <jallison@ciq.com>,
"Stuart Hayes" <stuart.w.hayes@gmail.com>,
"Laurence Oberman" <loberman@redhat.com>,
"Pasha Tatashin" <tatashin@google.com>
Subject: Re: [PATCH 7/9] PCI: Link a virtual function to its physical function
Date: Thu, 17 Sep 2026 16:44:44 +0000 [thread overview]
Message-ID: <20260917164444.B74B31F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917163744.191748-8-djeffery@redhat.com>
> With a PCI virtual function having the same bus for its parent
> as the physical function it is associated with, there is no
> explicit dependency between the two in the device tree. With
> async shutdown, this can result in the PF being shutdown before the
> VF has an opportunity to shutdown.
>
> Link the VF as a consumer of the PF to note its dependency and
> ensure clean shutdown ordering.
>
> Signed-off-by: Tarun Sahu <tarunsahu@google.com>
> Signed-off-by: David Jeffery <djeffery@redhat.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917163744.191748-1-djeffery@redhat.com?part=7
next prev parent reply other threads:[~2026-09-17 16:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 16:37 [PATCH v22 0/9] shut down devices asynchronously David Jeffery
2026-09-17 16:37 ` [PATCH 1/9] driver core: rely on put_device to free dev->p David Jeffery
2026-09-17 16:45 ` sashiko-bot
2026-09-17 16:37 ` [PATCH 2/9] driver core: prevent device_add() during system shutdown David Jeffery
2026-09-17 16:46 ` sashiko-bot
2026-09-17 16:37 ` [PATCH 3/9] driver core: warn should device_move try to move a need_parent_lock device David Jeffery
2026-09-17 16:47 ` sashiko-bot
2026-09-17 16:37 ` [PATCH 4/9] driver core: separate function to shutdown one device David Jeffery
2026-09-17 16:40 ` sashiko-bot
2026-09-17 16:37 ` [PATCH 5/9] driver core: do not always lock parent in shutdown David Jeffery
2026-09-17 16:46 ` sashiko-bot
2026-09-17 16:37 ` [PATCH 6/9] driver core: async device shutdown infrastructure David Jeffery
2026-09-17 16:47 ` sashiko-bot
2026-09-17 16:37 ` [PATCH 7/9] PCI: Link a virtual function to its physical function David Jeffery
2026-09-17 16:44 ` sashiko-bot [this message]
2026-09-17 16:37 ` [PATCH 8/9] PCI: Enable async shutdown support David Jeffery
2026-09-17 16:48 ` sashiko-bot
2026-09-17 16:37 ` [PATCH 9/9] scsi: " David Jeffery
2026-09-17 16:58 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2026-09-02 17:07 [PATCH v21 0/9] shut down devices asynchronously David Jeffery
2026-09-02 17:07 ` [PATCH 7/9] PCI: Link a virtual function to its physical function David Jeffery
2026-09-03 22:12 ` Bjorn Helgaas
2026-08-21 14:24 [PATCH v20 0/9] shut down devices asynchronously David Jeffery
2026-08-21 14:24 ` [PATCH 7/9] PCI: Link a virtual function to its physical function 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=20260917164444.B74B31F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bhelgaas@google.com \
--cc=bvanassche@acm.org \
--cc=dakr@kernel.org \
--cc=djeffery@redhat.com \
--cc=driver-core@lists.linux.dev \
--cc=emilne@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=jallison@ciq.com \
--cc=jmeneghi@redhat.com \
--cc=john.g.garry@oracle.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=mlombard@redhat.com \
--cc=rafael@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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
all inboxes | Powered by JetHome®