From: Sasha Levin <sashal@kernel.org>
To: Andrea Parri <parri.andrea@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org,
"K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Michael Kelley <mikelley@microsoft.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Dexuan Cui <decui@microsoft.com>, Wei Liu <wei.liu@kernel.org>
Subject: Re: [PATCH v3 0/3] Drivers: hv: vmbus: Miscellaneous improvements
Date: Mon, 28 Oct 2019 12:26:45 -0400 [thread overview]
Message-ID: <20191028162645.GH1554@sasha-vm> (raw)
In-Reply-To: <20191015114646.15354-1-parri.andrea@gmail.com>
On Tue, Oct 15, 2019 at 01:46:43PM +0200, Andrea Parri wrote:
>Hi all,
>
>The patchset:
>
> - refactors the VMBus negotiation code by introducing the table of
> VMBus protocol versions (patch 1/3),
>
> - enables VMBus protocol version 4.1, 5.1 and 5.2 (patch 2/3),
>
> - introduces a module parameter to cap the VMBus protocol versions
> which a guest can negotiate with the hypervisor (patch 3/3).
Queued up for hyperv-next, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-10-28 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 11:46 [PATCH v3 0/3] Drivers: hv: vmbus: Miscellaneous improvements Andrea Parri
2019-10-15 11:46 ` [PATCH v3 1/3] Drivers: hv: vmbus: Introduce table of VMBus protocol versions Andrea Parri
2019-10-15 13:08 ` Michael Kelley
2019-10-15 11:46 ` [PATCH v3 2/3] Drivers: hv: vmbus: Enable VMBus protocol versions 4.1, 5.1 and 5.2 Andrea Parri
2019-10-15 13:12 ` Michael Kelley
2019-10-15 11:46 ` [PATCH v3 3/3] Drivers: hv: vmbus: Add module parameter to cap the VMBus version Andrea Parri
2019-10-15 13:15 ` Michael Kelley
2019-10-15 14:26 ` [PATCH v3 0/3] Drivers: hv: vmbus: Miscellaneous improvements Wei Liu
2019-10-28 16:26 ` Sasha Levin [this message]
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=20191028162645.GH1554@sasha-vm \
--to=sashal@kernel.org \
--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=mikelley@microsoft.com \
--cc=parri.andrea@gmail.com \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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