From: Wei Liu <wei.liu@kernel.org>
To: Michael Kelley <mikelley@microsoft.com>, g@liuwe-devbox-debian-v2
Cc: Dexuan Cui <decui@microsoft.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
"hpa@zytor.com" <hpa@zytor.com>,
KY Srinivasan <kys@microsoft.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Hemminger <sthemmin@microsoft.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>, vkuznets <vkuznets@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"ohering@suse.com" <ohering@suse.com>,
"jwiesner@suse.com" <jwiesner@suse.com>,
"marcelo.cerri@canonical.com" <marcelo.cerri@canonical.com>
Subject: Re: [PATCH] x86/hyperv: Initialize clockevents after LAPIC is initialized
Date: Sun, 17 Jan 2021 15:22:36 +0000 [thread overview]
Message-ID: <20210117152236.nyoxxcs4c2hontm6@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <MWHPR21MB15930BECFDF0251D36CFBB98D7A69@MWHPR21MB1593.namprd21.prod.outlook.com>
On Sat, Jan 16, 2021 at 10:48:04PM +0000, Michael Kelley wrote:
> From: Dexuan Cui <decui@microsoft.com> Sent: Saturday, January 16, 2021 2:32 PM
> >
> > Fixes: 4df4cb9e99f8 ("x86/hyperv: Initialize clockevents earlier in CPU onlining")
> > Signed-off-by: Dexuan Cui <decui@microsoft.com>
> > ---
> > arch/x86/hyperv/hv_init.c | 29 ++++++++++++++++++++++++++---
> > 1 file changed, 26 insertions(+), 3 deletions(-)
> >
>
> Reviewed-by: Michael Kelley <mikelley@microsoft.com>
Applied to hyperv-fixes. Thanks.
>
prev parent reply other threads:[~2021-01-17 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 22:31 [PATCH] x86/hyperv: Initialize clockevents after LAPIC is initialized Dexuan Cui
2021-01-16 22:48 ` Michael Kelley
2021-01-17 15:22 ` 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=20210117152236.nyoxxcs4c2hontm6@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=bp@alien8.de \
--cc=decui@microsoft.com \
--cc=g@liuwe-devbox-debian-v2 \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jwiesner@suse.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=mikelley@microsoft.com \
--cc=ohering@suse.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.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).