From: Dexuan Cui <decui@microsoft.com>
To: "longli@linuxonhyperv.com" <longli@linuxonhyperv.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Long Li <longli@microsoft.com>
Subject: RE: [Patch v2 2/2] PCI: hv: Remove unused refcount and supporting functions for handling bus device removal
Date: Fri, 23 Apr 2021 07:18:22 +0000 [thread overview]
Message-ID: <MW2PR2101MB0892BE19CBB08214B7FEA5E9BF459@MW2PR2101MB0892.namprd21.prod.outlook.com> (raw)
In-Reply-To: <1619070346-21557-2-git-send-email-longli@linuxonhyperv.com>
> From: longli@linuxonhyperv.com <longli@linuxonhyperv.com>
> Sent: Wednesday, April 21, 2021 10:46 PM
>
> With the new method of flushing/stopping the workqueue before doing bus
> removal, the old mechanisum of using refcount and wait for completion
mechanisum -> mechanism
> is no longer needed. Remove those dead code.
>
> Signed-off-by: Long Li <longli@microsoft.com>
> ---
The patch looks good to me. BTW, can we also remove get_pcichild() and
put_pcichild() in an extra patch? I suspect we don't really need those either.
next prev parent reply other threads:[~2021-04-23 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 5:45 [Patch v2 1/2] PCI: hv: Fix a race condition when removing the device longli
2021-04-22 5:45 ` [Patch v2 2/2] PCI: hv: Remove unused refcount and supporting functions for handling bus device removal longli
2021-04-23 7:18 ` Dexuan Cui [this message]
2021-04-23 18:40 ` Long Li
2021-04-25 2:57 ` Dexuan Cui
2021-04-23 7:09 ` [Patch v2 1/2] PCI: hv: Fix a race condition when removing the device Dexuan Cui
2021-04-23 18:32 ` Long Li
2021-04-23 18:41 ` Dexuan Cui
2021-04-23 18:49 ` Long Li
2021-04-25 2:24 ` Dexuan Cui
2021-04-25 4:53 ` Long Li
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=MW2PR2101MB0892BE19CBB08214B7FEA5E9BF459@MW2PR2101MB0892.namprd21.prod.outlook.com \
--to=decui@microsoft.com \
--cc=bhelgaas@google.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).