From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Wei Hu <weh@microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, wei.liu@kernel.org, robh@kernel.org,
bhelgaas@google.com, linux-hyperv@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
decui@microsoft.com, mikelley@microsoft.com
Subject: Re: [PATCH v3 0/2] Fix PCI HyperV device error handling
Date: Mon, 11 May 2020 12:21:47 +0100 [thread overview]
Message-ID: <20200511112147.GD24954@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200507050126.10871-1-weh@microsoft.com>
On Thu, May 07, 2020 at 01:01:26PM +0800, Wei Hu wrote:
> This series better handles some PCI HyperV error cases in general
> and for kdump case. Some of review comments from previous individual
> patch reviews, including splitting into separate patches, have already
> been incorporated. Thanks Lorenzo Pieralisi for the review and
> suggestions, as well as Michael Kelley's contribution to the commit
> log.
>
> Thanks,
> Wei
>
>
> Wei Hu (2):
> PCI: hv: Fix the PCI HyperV probe failure path to release resource
> properly
> PCI: hv: Retry PCI bus D0 entry when the first attempt failed with
> invalid device state
>
> drivers/pci/controller/pci-hyperv.c | 60 ++++++++++++++++++++++++++---
> 1 file changed, 54 insertions(+), 6 deletions(-)
Applied to pci/hv, thanks.
Lorenzo
next prev parent reply other threads:[~2020-05-11 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 5:01 [PATCH v3 0/2] Fix PCI HyperV device error handling Wei Hu
2020-05-11 11:21 ` Lorenzo Pieralisi [this message]
2020-05-21 2:39 ` Michael Kelley
2020-05-21 17:42 ` Lorenzo Pieralisi
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=20200511112147.GD24954@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=decui@microsoft.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=mikelley@microsoft.com \
--cc=robh@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=weh@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).