From: chris.wei.cui@gmail.com
To: corbet@lwn.net, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Cui Wei <chris.wei.cui@gmail.com>
Subject: [PATCH] Documentation: fix speculation.rst chapter
Date: Sat, 26 Apr 2025 21:56:09 +0800 [thread overview]
Message-ID: <20250426135609.735-1-chris.wei.cui@gmail.com> (raw)
From: Cui Wei <chris.wei.cui@gmail.com>
'Mitigating speculation side-channels' should be a chapter rather
than title.
Signed-off-by: Cui Wei <chris.wei.cui@gmail.com>
---
Documentation/staging/speculation.rst | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/staging/speculation.rst b/Documentation/staging/speculation.rst
index 8045d99bcf12..0d526ba55d14 100644
--- a/Documentation/staging/speculation.rst
+++ b/Documentation/staging/speculation.rst
@@ -63,7 +63,6 @@ of an out-of-bounds address, while the second call will influence
microarchitectural state dependent on this value. This may provide an
arbitrary read primitive.
-====================================
Mitigating speculation side-channels
====================================
--
2.43.0
next reply other threads:[~2025-04-26 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 13:56 chris.wei.cui [this message]
2025-04-28 23:13 ` [PATCH] Documentation: fix speculation.rst chapter Jonathan Corbet
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=20250426135609.735-1-chris.wei.cui@gmail.com \
--to=chris.wei.cui@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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