public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kys@linuxonhyperv.com
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
	jasowang@redhat.com, sthemmin@microsoft.com,
	Michael.H.Kelley@microsoft.com, vkuznets@redhat.com
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Subject: [PATCH 0/8] Drivers: hv: Miscellaneous fixes/improvements
Date: Tue,  5 Jun 2018 13:35:36 -0700	[thread overview]
Message-ID: <20180605203536.29751-1-kys@linuxonhyperv.com> (raw)

From: "K. Y. Srinivasan" <kys@microsoft.com>

Some miscellaneous fixes/improvements. 

Arjan van de Ven (1):
  use the new async probing feature for the hyperv drivers

Dexuan Cui (1):
  Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()

Michael Kelley (4):
  x86/hyperv: Add interrupt handler annotations
  Drivers: hv: vmbus: Add comments on ring buffer signaling
  Drivers: hv: vmbus: Remove x86 MSR refs in arch independent code
  Drivers: hv: vmbus: Make TLFS #define names architecture neutral

Olaf Hering (1):
  tools: hv: update lsvmbus to be compatible with python3

Vitaly Kuznetsov (1):
  Tools: hv: vss: fix loop device detection

 arch/x86/hyperv/hv_init.c             |  4 +-
 arch/x86/include/asm/hyperv-tlfs.h    | 12 ++---
 arch/x86/include/asm/mshyperv.h       | 12 +++--
 arch/x86/kernel/cpu/mshyperv.c        |  6 +--
 drivers/hid/hid-hyperv.c              |  3 ++
 drivers/hv/channel_mgmt.c             |  4 +-
 drivers/hv/hv.c                       | 30 ++++++-------
 drivers/hv/hv_balloon.c               |  3 ++
 drivers/hv/hv_util.c                  |  3 ++
 drivers/hv/ring_buffer.c              | 65 ++++++++++++++++++++++-----
 drivers/input/serio/hyperv-keyboard.c |  3 ++
 drivers/net/hyperv/netvsc_drv.c       |  3 ++
 drivers/scsi/storvsc_drv.c            |  3 ++
 drivers/video/fbdev/hyperv_fb.c       |  6 +++
 include/linux/hyperv.h                | 31 +++++++++----
 tools/hv/hv_vss_daemon.c              | 65 +++++++++++++++++++++++++--
 tools/hv/lsvmbus                      | 12 ++---
 17 files changed, 201 insertions(+), 64 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-06-05 20:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 20:35 kys [this message]
2018-06-05 20:37 ` [PATCH 1/8] use the new async probing feature for the hyperv drivers kys
2018-06-05 20:37   ` [PATCH 2/8] x86/hyperv: Add interrupt handler annotations kys
2018-06-05 20:37   ` [PATCH 3/8] Drivers: hv: vmbus: Add comments on ring buffer signaling kys
2018-06-05 20:37   ` [PATCH 4/8] Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer() kys
2018-06-05 20:37   ` [PATCH 5/8] Drivers: hv: vmbus: Remove x86 MSR refs in arch independent code kys
2018-06-05 20:37   ` [PATCH 6/8] Drivers: hv: vmbus: Make TLFS #define names architecture neutral kys
2018-06-05 20:37   ` [PATCH 7/8] tools: hv: update lsvmbus to be compatible with python3 kys
2018-06-05 20:37   ` [PATCH 8/8] Tools: hv: vss: fix loop device detection kys

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=20180605203536.29751-1-kys@linuxonhyperv.com \
    --to=kys@linuxonhyperv.com \
    --cc=Michael.H.Kelley@microsoft.com \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --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