All of lore.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,
	vkuznets@redhat.com, jasowang@redhat.com,
	leann.ogasawara@canonical.com, marcelo.cerri@canonical.com,
	sthemmin@microsoft.com
Subject: [PATCH 0/4] Drivers: hv: vmbus: Miscellaneous fixes
Date: Tue, 27 Mar 2018 14:58:59 -0700	[thread overview]
Message-ID: <20180327215859.19624-1-kys@linuxonhyperv.com> (raw)

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

Some miscellaneous fixes and adjustments.

Dexuan Cui (2):
  Drivers: hv: vmbus: respect what we get from hv_get_synint_state()
  Drivers: hv: vmbus: do not mark HV_PCIE as perf_device

Stephen Hemminger (2):
  hv: add SPDX license to trace
  hv: add SPDX license id to Kconfig

 drivers/hv/Kconfig        | 2 ++
 drivers/hv/channel_mgmt.c | 2 +-
 drivers/hv/hv.c           | 1 -
 drivers/hv/hv_trace.c     | 2 ++
 drivers/hv/hv_trace.h     | 2 ++
 5 files changed, 7 insertions(+), 2 deletions(-)

-- 
2.15.1

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

             reply	other threads:[~2018-03-27 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 21:58 kys [this message]
2018-03-27 22:01 ` [PATCH 1/4] Drivers: hv: vmbus: respect what we get from hv_get_synint_state() kys
2018-03-27 22:01   ` [PATCH 2/4] Drivers: hv: vmbus: do not mark HV_PCIE as perf_device kys
2018-03-27 22:01   ` [PATCH 3/4] hv: add SPDX license to trace kys
2018-03-27 22:01   ` [PATCH 4/4] hv: add SPDX license id to Kconfig kys
  -- strict thread matches above, loose matches on Subject: below --
2017-03-05  1:13 [PATCH 0/4] Drivers: hv: vmbus: Miscellaneous Fixes 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=20180327215859.19624-1-kys@linuxonhyperv.com \
    --to=kys@linuxonhyperv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.