From: Wei Liu <wei.liu@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Wei Liu <wei.liu@kernel.org>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
kys@microsoft.com, haiyangz@microsoft.com, 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 1/5] x86/init: Make get/set_rtc_noop() public
Date: Thu, 13 Apr 2023 15:39:16 +0000 [thread overview]
Message-ID: <ZDgiJNNoqGbd7YTA@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20230413153753.GDZDgh0T5acw2v1KjK@fat_crate.local>
On Thu, Apr 13, 2023 at 05:37:53PM +0200, Borislav Petkov wrote:
> On Thu, Apr 13, 2023 at 03:34:33PM +0000, Wei Liu wrote:
> > On Thu, Apr 13, 2023 at 11:19:42AM +0200, Borislav Petkov wrote:
> > > On Thu, Apr 13, 2023 at 01:16:07AM +0000, Wei Liu wrote:
> > > > On Mon, Apr 10, 2023 at 10:55:28PM -0700, Saurabh Sengar wrote:
> > > > > Make get/set_rtc_noop() to be public so that they can be used
> > > > > in other modules as well.
> > > > >
> > > > > Co-developed-by: Tianyu Lan <tiala@microsoft.com>
> > > > > Signed-off-by: Tianyu Lan <tiala@microsoft.com>
> > > > > Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
> > > > > Reviewed-by: Wei Liu <wei.liu@kernel.org>
> > > > > Reviewed-by: Michael Kelley <mikelley@microsoft.com>
> > > >
> > > > x86 maintainers, can you please ack or nack this patch?
> > >
> > > Acked-by: Borislav Petkov (AMD) <bp@alien8.de>
> >
> > Thank you very much!
>
> Just a heads up:
>
> https://git.kernel.org/tip/775d3c514c5b2763a50ab7839026d7561795924d
>
> and that one is a fix so it'll go to Linus now.
>
> Which means, you'll have to use Linus' tree with that fix as a base and
> queue everything ontop.
Okay, understood. Thanks.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-04-13 15:39 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 [this message]
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 ` [PATCH v5 0/5] Hyper-V VTL support 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=ZDgiJNNoqGbd7YTA@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).