From: Jonathan Corbet <corbet@lwn.net>
To: pierwill <pierwill@protonmail.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Cc: "bp@alien8.de" <bp@alien8.de>,
"peterz@infradead.org" <peterz@infradead.org>,
"jpoimboe@kernel.org" <jpoimboe@kernel.org>,
"pawan.kumar.gupta@linux.intel.com"
<pawan.kumar.gupta@linux.intel.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] docs: Fix missing word in spectre.rst
Date: Mon, 10 Nov 2025 12:39:31 -0700 [thread overview]
Message-ID: <87qzu5y8wc.fsf@trenco.lwn.net> (raw)
In-Reply-To: <Ru-d3ltJIyY4Oc6tzHwpSiDeFwSLHEzd7Utcr6iobgIy1B8wLRI4f6JiCb0a9n-0-r19d0dyLL3yS8KWVcyHfpkyDErWXYTkI3AJfUPTNCc=@protonmail.com>
pierwill <pierwill@protonmail.com> writes:
> Corrects a missing word in the hardware vulnerability docs.
>
> Signed-off-by: Will Pierce <pierwill@protonmail.com>
> ---
> Documentation/admin-guide/hw-vuln/spectre.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/hw-vuln/spectre.rst b/Documentation/admin-guide/hw-vuln/spectre.rst
> index 991f12adef8d..4bb8549bee82 100644
> --- a/Documentation/admin-guide/hw-vuln/spectre.rst
> +++ b/Documentation/admin-guide/hw-vuln/spectre.rst
> @@ -406,7 +406,7 @@ The possible values in this file are:
>
> - Single threaded indirect branch prediction (STIBP) status for protection
> between different hyper threads. This feature can be controlled through
> - prctl per process, or through kernel command line options. This is x86
> + prctl per process, or through kernel command line options. This is an x86
Applied, thanks.
jon
prev parent reply other threads:[~2025-11-10 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 2:34 pierwill
2025-11-10 19:39 ` Jonathan Corbet [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=87qzu5y8wc.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bp@alien8.de \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=pierwill@protonmail.com \
--cc=tglx@linutronix.de \
/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®