From: kys@exchange.microsoft.com
To: gregkh@linuxfoundation.org, 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
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Subject: [PATCH 0/5] Drivers: hv: Miscellaneous fixes
Date: Sat, 9 Sep 2017 22:53:18 -0700 [thread overview]
Message-ID: <20170910055318.31655-1-kys@exchange.microsoft.com> (raw)
From: "K. Y. Srinivasan" <kys@microsoft.com>
Miscellaneous fixes.
Dexuan Cui (2):
vmbus: don't acquire the mutex in vmbus_hvsock_device_unregister()
vmbus: suppress uevents for hv_sock devices
Olaf Hering (1):
Drivers: hv: fcopy: restore correct transfer length
Stephen Hemminger (2):
vmbus: add per-channel sysfs info
Drivers: hv: vmbus: Expose per-channel interrupts and events counters
Documentation/ABI/stable/sysfs-bus-vmbus | 70 +++++++++++
drivers/hv/channel_mgmt.c | 14 ++-
drivers/hv/connection.c | 2 +
drivers/hv/hv_fcopy.c | 4 +
drivers/hv/hyperv_vmbus.h | 2 +
drivers/hv/vmbus_drv.c | 205 +++++++++++++++++++++++++++++--
include/linux/hyperv.h | 10 ++
7 files changed, 290 insertions(+), 17 deletions(-)
--
2.14.1
next reply other threads:[~2017-09-10 5:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 5:53 kys [this message]
2017-09-10 6:08 ` [PATCH 1/5] vmbus: don't acquire the mutex in vmbus_hvsock_device_unregister() kys
2017-09-10 6:08 ` [PATCH 2/5] vmbus: suppress uevents for hv_sock devices kys
2017-09-10 8:09 ` Greg KH
2017-09-18 0:02 ` KY Srinivasan
2017-09-10 6:08 ` [PATCH 3/5] Drivers: hv: fcopy: restore correct transfer length kys
2017-09-10 6:08 ` [PATCH 4/5] vmbus: add per-channel sysfs info kys
2017-09-10 6:08 ` [PATCH 5/5] Drivers: hv: vmbus: Expose per-channel event counters kys
-- strict thread matches above, loose matches on Subject: below --
2018-10-17 3:12 [PATCH 0/5] Drivers: hv: Miscellaneous fixes kys
2017-08-06 20:12 kys
2015-09-16 0:37 K. Y. 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=20170910055318.31655-1-kys@exchange.microsoft.com \
--to=kys@exchange.microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).