From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
Ashok Raj <ashok.raj@intel.com>, Borislav Petkov <bp@suse.de>,
x86@kernel.org
Subject: Re: [tip: x86/microcode] x86/microcode: Document the whole late loading problem
Date: Tue, 16 Aug 2022 08:51:12 +0200 [thread overview]
Message-ID: <Yvs+YG0eTBYm1kI9@gmail.com> (raw)
In-Reply-To: <166059240569.401.7221163581479146132.tip-bot2@tip-bot2>
* tip-bot2 for Ashok Raj <tip-bot2@linutronix.de> wrote:
> Builtin microcode
> =================
>
> @@ -134,7 +232,7 @@ This basically means, you have the following tree structure locally::
> | |-- 06-3a-09
> ...
>
> -so that the build system can find those files and integrate them into
> +So that the build system can find those files and integrate them into
> the final kernel image. The early loader finds them and applies them.
Small nit: this capitalization change is spurious. The 'so' is a
continuation of the sentence, not a separate sentence - now that paragraph
is actively weird & grammatically incorrect, starting with a 'So'.
Maybe:
... so that the build system can find those files and integrate them into
Thanks,
Ingo
next prev parent reply other threads:[~2022-08-16 8:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 22:38 [PATCH 0/5] Adding more robustness to microcode loading Ashok Raj
2022-08-13 22:38 ` [PATCH 1/5] x86/microcode: Add missing documentation that late-load will taint kernel Ashok Raj
2022-08-15 19:40 ` [tip: x86/microcode] x86/microcode: Document the whole late loading problem tip-bot2 for Ashok Raj
2022-08-16 3:21 ` Ashok Raj
2022-08-16 7:40 ` Borislav Petkov
2022-08-16 6:51 ` Ingo Molnar [this message]
2022-08-16 7:46 ` tip-bot2 for Ashok Raj
2022-08-18 14:04 ` tip-bot2 for Ashok Raj
2022-08-13 22:38 ` [PATCH 2/5] x86/microcode/intel: Check against CPU signature before saving microcode Ashok Raj
2022-08-13 22:38 ` [PATCH 3/5] x86/microcode/intel: Allow a late-load only if a min rev is specified Ashok Raj
2022-08-15 7:43 ` Peter Zijlstra
2022-08-15 12:29 ` Ashok Raj
2022-08-15 7:46 ` Peter Zijlstra
2022-08-15 12:41 ` Ashok Raj
2022-08-15 13:04 ` Peter Zijlstra
2022-08-18 17:34 ` Dave Hansen
2022-08-13 22:38 ` [PATCH 4/5] x86/microcode: Avoid any chance of MCE's during microcode update Ashok Raj
2022-08-13 22:38 ` [PATCH 5/5] x86/microcode: Handle NMI's " Ashok Raj
2022-08-14 0:13 ` Andy Lutomirski
2022-08-14 1:19 ` Andy Lutomirski
2022-08-14 3:05 ` Ashok Raj
2022-08-14 2:54 ` Ashok Raj
2022-08-14 11:58 ` Andrew Cooper
2022-08-14 14:41 ` Ashok Raj
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=Yvs+YG0eTBYm1kI9@gmail.com \
--to=mingo@kernel.org \
--cc=ashok.raj@intel.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.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