From: Long Li <longli@microsoft.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "longli@linuxonhyperv.com" <longli@linuxonhyperv.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Sasha Levin <sashal@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Andrew Murray <andrew.murray@arm.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>
Subject: RE: [Patch v3 1/2] PCI: hv: Decouple the func definition in hv_dr_state from VSP message
Date: Mon, 13 Jan 2020 19:30:33 +0000 [thread overview]
Message-ID: <BL0PR2101MB1123E4716CFCB1990968D4FACE350@BL0PR2101MB1123.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20200111175341.GA238104@google.com>
>Subject: Re: [Patch v3 1/2] PCI: hv: Decouple the func definition in hv_dr_state
>from VSP message
>
>On Sat, Jan 11, 2020 at 08:27:25AM +0000, Long Li wrote:
>> Hi Bjorn,
>>
>> I have addressed all the prior comments in this v3 patch. Please take a look.
>
>Lorenzo normally merges hv updates, so I'm sure this is on his list to take a look.
>I pointed out a few spelling and similar nits, but I didn't review the actual
>substance of v3.
>
>Bjorn
Thanks, I will address your comments and send v4.
Long
next prev parent reply other threads:[~2020-01-13 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 19:40 [Patch v3 1/2] PCI: hv: Decouple the func definition in hv_dr_state from VSP message longli
2019-12-26 19:40 ` [Patch v3 2/2] PCI: hv: Add support for protocol 1.3 and support PCI_BUS_RELATIONS2 longli
2020-01-11 17:51 ` Bjorn Helgaas
2020-01-11 8:27 ` [Patch v3 1/2] PCI: hv: Decouple the func definition in hv_dr_state from VSP message Long Li
2020-01-11 17:53 ` Bjorn Helgaas
2020-01-13 19:30 ` Long Li [this message]
2020-01-11 17:49 ` Bjorn Helgaas
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=BL0PR2101MB1123E4716CFCB1990968D4FACE350@BL0PR2101MB1123.namprd21.prod.outlook.com \
--to=longli@microsoft.com \
--cc=andrew.murray@arm.com \
--cc=haiyangz@microsoft.com \
--cc=helgaas@kernel.org \
--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=lorenzo.pieralisi@arm.com \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.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;
as well as URLs for NNTP newsgroup(s).