From: Borislav Petkov <bp@alien8.de>
To: Mike Travis <mike.travis@hpe.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Steve Wahl <steve.wahl@hpe.com>,
x86@kernel.org, Andy Shevchenko <andy@infradead.org>,
Darren Hart <dvhart@infradead.org>,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Russ Anderson <russ.anderson@hpe.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v3 0/3] x86/platform/uv: UV Kernel support for UV5
Date: Tue, 5 Apr 2022 10:50:53 +0200 [thread overview]
Message-ID: <YkwC7TCRMM0ejFvh@zn.tnic> (raw)
In-Reply-To: <20220318224304.174967-1-mike.travis@hpe.com>
On Fri, Mar 18, 2022 at 05:43:01PM -0500, Mike Travis wrote:
> Mike Travis (3):
> x86/platform/uv: Update NMI Handler for UV5
> x86/platform/uv: Update TSC sync state for UV5
> x86/platform/uv: Log gap hole end size
>
> arch/x86/kernel/apic/x2apic_uv_x.c | 20 +++++++++++++++-----
> arch/x86/platform/uv/uv_nmi.c | 21 +++++++++++----------
> 2 files changed, 26 insertions(+), 15 deletions(-)
All three zapped from tip until
https://lore.kernel.org/r/87zgl02w6v.ffs@tglx
is resolved.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-04-05 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 22:43 [PATCH v3 0/3] x86/platform/uv: UV Kernel support for UV5 Mike Travis
2022-03-18 22:43 ` [PATCH v3 1/3] x86/platform/uv: Update NMI Handler " Mike Travis
2022-03-18 22:43 ` [PATCH v3 2/3] x86/platform/uv: Update TSC sync state " Mike Travis
2022-03-18 22:43 ` [PATCH v3 3/3] x86/platform/uv: Log gap hole end size Mike Travis
2022-04-05 8:50 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-04 17:41 [PATCH v3 0/3] x86/platform/uv: UV Kernel support for UV5 Mike Travis
2022-04-04 17:48 ` Borislav Petkov
2022-04-04 17:56 ` Travis, Mike
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=YkwC7TCRMM0ejFvh@zn.tnic \
--to=bp@alien8.de \
--cc=andy@infradead.org \
--cc=dimitri.sivanich@hpe.com \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=russ.anderson@hpe.com \
--cc=steve.wahl@hpe.com \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.