From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@microsoft.com, linux-hyperv@vger.kernel.org,
kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Hyper-V commits for 5.2
Date: Fri, 24 May 2019 20:28:02 +0200 [thread overview]
Message-ID: <20190524182802.GA7887@kroah.com> (raw)
In-Reply-To: <20190506033111.A3EBA205F4@mail.kernel.org>
On Sun, May 05, 2019 at 11:31:04PM -0400, Sasha Levin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-next-signed
>
> for you to fetch changes up to a3fb7bf369efa296c1fc68aead1b6fb3c735573b:
>
> drivers: input: serio: Add a module desription to the hyperv_keyboard driver (2019-04-23 15:41:40 -0400)
>
> - ----------------------------------------------------------------
> Adding module description to various hyper-v modules
>
> - ----------------------------------------------------------------
> Joseph Salisbury (3):
> drivers: hid: Add a module description line to the hid_hyperv driver
> drivers: hv: Add a module description line to the hv_vmbus driver
> drivers: input: serio: Add a module desription to the hyperv_keyboard driver
>
> drivers/hid/hid-hyperv.c | 2 ++
> drivers/hv/vmbus_drv.c | 1 +
> drivers/input/serio/hyperv-keyboard.c | 2 ++
This should go through the different subsystems, for the different
drivers, not just through me.
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-24 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 3:31 [GIT PULL] Hyper-V commits for 5.2 Sasha Levin
2019-05-24 18:28 ` Greg KH [this message]
2019-05-24 19:24 ` Sasha Levin
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=20190524182802.GA7887@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.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).