linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brendan Jackman <jackmanb@google.com>
To: Jonathan Corbet <corbet@lwn.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	 Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	 Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Balbir Singh <sblbir@amazon.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Brendan Jackman <jackmanb@google.com>,
	Kees Cook <kees@kernel.org>
Subject: [PATCH 0/2] Documentation: fixups for L1D flushing
Date: Wed, 15 Oct 2025 17:02:04 +0000	[thread overview]
Message-ID: <20251015-l1d-flush-doc-v1-0-f8cefea3f2f2@google.com> (raw)

Signed-off-by: Brendan Jackman <jackmanb@google.com>
---
Brendan Jackman (2):
      Documentation: clarify PR_SPEC_L1D_FLUSH
      Documentation: fix reference to PR_SPEC_L1D_FLUSH

 Documentation/admin-guide/hw-vuln/l1d_flush.rst | 2 +-
 Documentation/userspace-api/spec_ctrl.rst       | 6 +++++-
 2 files changed, 6 insertions(+), 2 deletions(-)
---
base-commit: 0292ef418ce08aad597fc0bba65b6dbb841808ba
change-id: 20251015-l1d-flush-doc-029f64d2b0d3

Best regards,
-- 
Brendan Jackman <jackmanb@google.com>


             reply	other threads:[~2025-10-15 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 17:02 Brendan Jackman [this message]
2025-10-15 17:02 ` [PATCH 1/2] Documentation: clarify PR_SPEC_L1D_FLUSH Brendan Jackman
2025-10-15 21:41   ` Kees Cook
2025-10-15 23:42     ` Josh Poimboeuf
2025-10-16  8:28       ` Brendan Jackman
2025-10-15 17:02 ` [PATCH 2/2] Documentation: fix reference to PR_SPEC_L1D_FLUSH Brendan Jackman
2025-10-16 14:54 ` [PATCH 0/2] Documentation: fixups for L1D flushing Brendan Jackman
2025-10-30 14:00   ` Brendan Jackman
2025-10-29 16:15 ` 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=20251015-l1d-flush-doc-v1-0-f8cefea3f2f2@google.com \
    --to=jackmanb@google.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=jpoimboe@kernel.org \
    --cc=kees@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=sblbir@amazon.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;
as well as URLs for NNTP newsgroup(s).