From: Bjorn Helgaas <helgaas@kernel.org>
To: Anatoli Antonovitch <a.antonovitch@gmail.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com, lukas@wunner.de,
Alexander.Deucher@amd.com, christian.koenig@amd.com,
Anatoli Antonovitch <anatoli.antonovitch@amd.com>
Subject: Re: [PATCH] PCI/hotplug: Replaced down_write_nested with hotplug_slot_rwsem if ctrl->depth > 0 when taking the ctrl->reset_lock.
Date: Thu, 5 Jan 2023 13:18:52 -0600 [thread overview]
Message-ID: <20230105191852.GA1162145@bhelgaas> (raw)
In-Reply-To: <20230105184355.9829-1-a.antonovitch@gmail.com>
On Thu, Jan 05, 2023 at 01:43:55PM -0500, Anatoli Antonovitch wrote:
> From: Anatoli Antonovitch <anatoli.antonovitch@amd.com>
>
> It is to avoid any potential issues when S3 resume but at the same time we want to hot-unplug.
> Need to do some more testing to see if it is still necessary.
I'm not sure how to interpret this.
I guess I'll wait for you to do the testing and repost this if it does
turn out to be necessary?
I don't want to merge a patch with a commit log that says "need to do
more testing."
Bjorn
next prev parent reply other threads:[~2023-01-05 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 18:43 [PATCH] PCI/hotplug: Replaced down_write_nested with hotplug_slot_rwsem if ctrl->depth > 0 when taking the ctrl->reset_lock Anatoli Antonovitch
2023-01-05 19:18 ` Bjorn Helgaas [this message]
[not found] ` <5b9a2dc7-54ab-82c5-81e7-1770a4ec891c@amd.com>
2023-01-16 18:37 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 17:01 Anatoli Antonovitch
2023-01-20 9:28 ` Lukas Wunner
2023-01-20 21:35 ` Anatoli Antonovitch
2023-01-21 7:21 ` Lukas Wunner
2023-01-23 19:30 ` Anatoli Antonovitch
2023-02-13 14:59 ` Anatoli Antonovitch
2023-02-17 16:03 ` Bjorn Helgaas
2023-02-17 18:37 ` Deucher, Alexander
2023-02-19 20:21 ` Lukas Wunner
2023-04-10 20:36 ` Anatoli Antonovitch
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=20230105191852.GA1162145@bhelgaas \
--to=helgaas@kernel.org \
--cc=Alexander.Deucher@amd.com \
--cc=a.antonovitch@gmail.com \
--cc=anatoli.antonovitch@amd.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.