From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@microsoft.com
Cc: kys@microsoft.com
Cc: haiyangz@microsoft.com
Cc: sthemmin@microsoft.com
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Hyper-V commits for 5.0
Date: Wed, 09 Jan 2019 21:56:12 -0500 [thread overview]
Message-ID: <20190110025613.1E42020665@mail.kernel.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-fixes-signed
for you to fetch changes up to b5679cebf780c6f1c2451a73bf1842a4409840e7:
vmbus: fix subchannel removal (2019-01-09 19:20:31 -0500)
- ----------------------------------------------------------------
hyperv-fixes-signed
- ----------------------------------------------------------------
Dexuan Cui (2):
Drivers: hv: vmbus: Check for ring when getting debug info
vmbus: fix subchannel removal
Vitaly Kuznetsov (1):
hv_balloon: avoid touching uninitialized struct page during tail onlining
drivers/hv/channel.c | 9 +----
drivers/hv/hv_balloon.c | 10 +++---
drivers/hv/ring_buffer.c | 31 ++++++++---------
drivers/hv/vmbus_drv.c | 91 ++++++++++++++++++++++++++++++++----------------
include/linux/hyperv.h | 5 +--
5 files changed, 86 insertions(+), 60 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE4n5dijQDou9mhzu83qZv95d3LNwFAlw2tCsACgkQ3qZv95d3
LNyATg/9GIHd9dW3B7YcCQdxgnFJWNtEzHrPSx+qTstQE+wh3xD6Mv5W/81nfcYq
3FBlmFKEMTl9UWpVIZLF2aAKGFahlljJGNAmU2VSg9UCJQ4AtPKDWOdrn4o9go6R
VuAvkh0CXGyqZsO7rGUBnKLM3zA38eGoRZpSgAKe9pZfc4Uux7ibUnCzD2W2Ds/h
k8qYZDcmLHmQnqW4rywnkJ/YLe2wkhPEUYpq+fpUBmGU81S8QrSfBgDPrpz1NpEx
oBfZTwSx0Rk1u28+u/KhH7mOo5BnyS44MtgRmHdaEBhyGTP3gpkQgeZC5+hEV2qi
9ALvUNV80uh1Rv4cIHnFjGf8oFbdgFCVq/LQh+zYuJ8gsupoRmJjMJI4DmV1oviB
HhXE0rBmGHVOSe11dWyZOQR344pM0yxiB9jOooL54SKrulN8uidPUAETlsD5pfWc
yTF+3g40mv+hLAgxLu/j20PJmkIB2lR6m6wNe8+djnDKgs4TQLkTBBhJMaH1Uaf2
yad0jy1JTH0V0TUhCmvs49C++0OXGyS6N4yrNWISKGt+wo6c7lGMFJKVxKAGFkSt
NRw1muOa0AmypssbTqe6DCjtaX+q2U+/d1t85LdPIEOzrH4ukunVoXtuaWCXu5hQ
8cV93VXemBUaRurlCh2rrxt0p1RbOG+B1SsHAYTMOfQ0r3RHFfI=
=WONp
-----END PGP SIGNATURE-----
next reply other threads:[~2019-01-10 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 2:56 Sasha Levin [this message]
2019-01-10 6:54 ` Greg KH
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=20190110025613.1E42020665@mail.kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
Powered by JetHome