From: Saurabh Sengar <ssengar@linux.microsoft.com>
To: 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, tiala@microsoft.com, mikelley@microsoft.com,
linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org
Subject: [PATCH 0/2] Fix for applied series [PATCH v5 0/5] Hyper-V VTL support
Date: Mon, 17 Apr 2023 22:12:39 -0700 [thread overview]
Message-ID: <1681794761-13734-1-git-send-email-ssengar@linux.microsoft.com> (raw)
[PATCH v5 0/5] Hyper-V VTL support is already applied, however
there are couple of kernel test bot warning reported. This patch
series on top of [PATCH v5 0/5] Hyper-V VTL support fixes these.
I expect them to be squash commit on respective patches.
The first patch is to fix 1/5 of the series:
https://lore.kernel.org/all/1681192532-15460-2-git-send-email-ssengar@linux.microsoft.com/
The second patch is to fix 3/5 of the series:
https://lore.kernel.org/all/1681192532-15460-4-git-send-email-ssengar@linux.microsoft.com/
Saurabh Sengar (2):
x86/init: Remove static for get/set_rtc_noop()
x86/hyperv: Allow hv_get_nmi_reason compilation irrespective of HYPERV
config
arch/x86/include/asm/mshyperv.h | 10 +++++-----
arch/x86/kernel/x86_init.c | 4 ++--
2 files changed, 7 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2023-04-18 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 5:12 Saurabh Sengar [this message]
2023-04-18 5:12 ` [PATCH 1/2] x86/init: Remove static for get/set_rtc_noop() Saurabh Sengar
2023-04-18 5:12 ` [PATCH 2/2] x86/hyperv: Allow hv_get_nmi_reason compilation irrespective of HYPERV config Saurabh Sengar
2023-04-18 9:33 ` [PATCH 0/2] Fix for applied series [PATCH v5 0/5] Hyper-V VTL support Borislav Petkov
2023-04-18 16:17 ` Wei Liu
2023-04-18 17:27 ` Wei Liu
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=1681794761-13734-1-git-send-email-ssengar@linux.microsoft.com \
--to=ssengar@linux.microsoft.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tiala@microsoft.com \
--cc=wei.liu@kernel.org \
--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).