From: Greg KH <gregkh@linuxfoundation.org>
To: kys@microsoft.com
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
jasowang@redhat.com, leann.ogasawara@canonical.com,
marcelo.cerri@canonical.com, sthemmin@microsoft.com
Subject: Re: [PATCH 0/3] Drivers: hv: vmbus: Miscellaneous enhancements and fixes
Date: Fri, 20 Oct 2017 15:28:29 +0200 [thread overview]
Message-ID: <20171020132829.GB30700@kroah.com> (raw)
In-Reply-To: <20171006003359.24370-1-kys@exchange.microsoft.com>
On Thu, Oct 05, 2017 at 05:33:59PM -0700, kys@exchange.microsoft.com wrote:
> From: "K. Y. Srinivasan" <kys@microsoft.com>
>
> Miscellaneous enhancements and fixes.
>
> K. Y. Srinivasan (1):
> Drivers: hv: vmbus: Make pannic reporting to be more useful
>
> Stephen Hemminger (2):
> Drivers: hv: vmbus: Expose per-channel interrupts and events counters
> vmbus: initialize reserved fields in messages
>
Patch 2 of this series applied, the rest I'll expect a new version of.
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-20 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 0:33 [PATCH 0/3] Drivers: hv: vmbus: Miscellaneous enhancements and fixes kys
2017-10-06 0:35 ` [PATCH 1/3] Drivers: hv: vmbus: Expose per-channel interrupts and events counters kys
2017-10-06 0:35 ` [PATCH 2/3] vmbus: initialize reserved fields in messages kys
2017-10-06 0:35 ` [PATCH 3/3] Drivers: hv: vmbus: Make pannic reporting to be more useful kys
2017-10-12 13:39 ` Vitaly Kuznetsov
2017-10-12 15:06 ` KY Srinivasan
2017-10-20 13:27 ` [PATCH 1/3] Drivers: hv: vmbus: Expose per-channel interrupts and events counters Greg KH
2017-10-20 13:28 ` Greg KH [this message]
2017-10-20 21:35 ` [PATCH 0/3] Drivers: hv: vmbus: Miscellaneous enhancements and fixes KY Srinivasan
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=20171020132829.GB30700@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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