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, linux-kernel@vger.kernel.org,
Russ Anderson <rja@hpe.com>,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Russ Anderson <russ.anderson@hpe.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/platform/uv: Add set of kernel block size for hubless arches
Date: Fri, 5 Mar 2021 14:18:04 +0100 [thread overview]
Message-ID: <20210305131804.GA2685@zn.tnic> (raw)
In-Reply-To: <20210304223955.183463-1-mike.travis@hpe.com>
On Thu, Mar 04, 2021 at 04:39:55PM -0600, Mike Travis wrote:
> The commit below added a call to set the block size value that is needed
> to set the value used by the kernel. This was done for UV Hubbed systems.
> This commit adds that same set call to hubless systems which supports the
> same NVRAMS and Intel BIOS thus the same problem occurs.
>
> Fixes: bbbd2b51a2aa ...
The format is:
Fixes: bbbd2b51a2aa ("x86/platform/UV: Use new set memory block size function")
and you don't need to paste the commit text.
And if you add a Fixes tag, then this is supposed to fix something but
I'm unclear what exactly this fixes?
IOW, should this patch be backported to stable because UV hubless
systems would somehow fail without it?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2021-03-05 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 22:39 Mike Travis
2021-03-05 13:18 ` Borislav Petkov [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=20210305131804.GA2685@zn.tnic \
--to=bp@alien8.de \
--cc=dimitri.sivanich@hpe.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=mingo@redhat.com \
--cc=rja@hpe.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®