From: Wei Liu <wei.liu@kernel.org>
To: Saurabh Sengar <ssengar@linux.microsoft.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, arnd@arndb.de, tiala@microsoft.com,
mikelley@microsoft.com, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-arch@vger.kernel.org,
jgross@suse.com, mat.jonczyk@o2.pl
Subject: Re: [PATCH v5 0/5] Hyper-V VTL support
Date: Mon, 17 Apr 2023 19:26:54 +0000 [thread overview]
Message-ID: <ZD2dfuHFCJmOkGt9@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <1681192532-15460-1-git-send-email-ssengar@linux.microsoft.com>
On Mon, Apr 10, 2023 at 10:55:27PM -0700, Saurabh Sengar wrote:
[...]
> Saurabh Sengar (5):
> x86/init: Make get/set_rtc_noop() public
> x86/hyperv: Add VTL specific structs and hypercalls
> x86/hyperv: Make hv_get_nmi_reason public
> Drivers: hv: Kconfig: Add HYPERV_VTL_MODE
> x86/hyperv: VTL support for Hyper-V
>
Applied to hyperv-next. Thanks.
prev parent reply other threads:[~2023-04-17 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 5:55 [PATCH v5 0/5] Hyper-V VTL support Saurabh Sengar
2023-04-11 5:55 ` [PATCH v5 1/5] x86/init: Make get/set_rtc_noop() public Saurabh Sengar
2023-04-13 1:16 ` Wei Liu
2023-04-13 9:19 ` Borislav Petkov
2023-04-13 15:34 ` Wei Liu
2023-04-13 15:37 ` Borislav Petkov
2023-04-13 15:39 ` Wei Liu
2023-04-11 5:55 ` [PATCH v5 2/5] x86/hyperv: Add VTL specific structs and hypercalls Saurabh Sengar
2023-04-11 5:55 ` [PATCH v5 3/5] x86/hyperv: Make hv_get_nmi_reason public Saurabh Sengar
2023-04-11 5:55 ` [PATCH v5 4/5] Drivers: hv: Kconfig: Add HYPERV_VTL_MODE Saurabh Sengar
2023-04-11 5:55 ` [PATCH v5 5/5] x86/hyperv: VTL support for Hyper-V Saurabh Sengar
2023-04-17 19:26 ` Wei Liu [this message]
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=ZD2dfuHFCJmOkGt9@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mat.jonczyk@o2.pl \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=ssengar@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=tiala@microsoft.com \
--cc=x86@kernel.org \
/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).