From: Balbir Singh <sblbir@amazon.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>
Cc: <peterz@infradead.org>, <linux-kernel@vger.kernel.org>,
<keescook@chromium.org>, Balbir Singh <sblbir@amazon.com>
Subject: [PATCH v1 3/3] Documentation/l1d_flush: Fix up warning with labels
Date: Wed, 18 Nov 2020 10:49:34 +1100 [thread overview]
Message-ID: <20201117234934.25985-4-sblbir@amazon.com> (raw)
In-Reply-To: <20201117234934.25985-1-sblbir@amazon.com>
Add a label to spec_set_ctrl to remove the build warning.
Signed-off-by: Balbir Singh <sblbir@amazon.com>
---
To be applied on top of tip commit id
767d46ab566dd489733666efe48732d523c8c332
Documentation/admin-guide/hw-vuln/l1d_flush.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/hw-vuln/l1d_flush.rst b/Documentation/admin-guide/hw-vuln/l1d_flush.rst
index c6a0713c8271..108bd2bdc196 100644
--- a/Documentation/admin-guide/hw-vuln/l1d_flush.rst
+++ b/Documentation/admin-guide/hw-vuln/l1d_flush.rst
@@ -22,8 +22,8 @@ mechanism
Usage Guidelines
----------------
-Please see document: :ref:`Documentation/userspace-api/spec_ctrl.rst` for
-details.
+Please see document: :ref:`Documentation/userspace-api/spec_ctrl.rst
+<set_spec_ctrl>` for details.
**NOTE**: The feature is disabled by default, applications need to
specifically opt into the feature to enable it.
--
2.17.1
prev parent reply other threads:[~2020-11-17 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 23:49 [PATCH v1 0/3] Fixes to L1D flushing (on top of linux-next and Balbir Singh
2020-11-17 23:49 ` [PATCH v1 1/3] x86/mm: change l1d flush runtime prctl behaviour Balbir Singh
2020-11-17 23:49 ` [PATCH v1 2/3] Documentation: Update the new SIGBUS behaviour for tasks Balbir Singh
2020-11-17 23:49 ` Balbir Singh [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=20201117234934.25985-4-sblbir@amazon.com \
--to=sblbir@amazon.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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