From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH] tools: docs: memory-model: fix references for some files
Date: Wed, 26 Aug 2020 12:47:40 +0200 [thread overview]
Message-ID: <20200826104740.532184-1-mchehab+huawei@kernel.org> (raw)
- The sysfs.txt file was converted to ReST and renamed;
- The control-dependencies.txt is not at
Documentation/control-dependencies.txt. As it is at the
same dir as the README file, which mentions it, just
remove Documentation/.
With that, ./scripts/documentation-file-ref-check script
is now happy again for files under tools/.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
tools/memory-model/Documentation/README | 2 +-
tools/memory-model/Documentation/ordering.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/memory-model/Documentation/README b/tools/memory-model/Documentation/README
index 16177aaa9752..004969992bac 100644
--- a/tools/memory-model/Documentation/README
+++ b/tools/memory-model/Documentation/README
@@ -55,7 +55,7 @@ README
Documentation/cheatsheet.txt
Quick-reference guide to the Linux-kernel memory model.
-Documentation/control-dependencies.txt
+control-dependencies.txt
A guide to preventing compiler optimizations from destroying
your control dependencies.
diff --git a/tools/memory-model/Documentation/ordering.txt b/tools/memory-model/Documentation/ordering.txt
index 4b2cc551103a..5a87d7384758 100644
--- a/tools/memory-model/Documentation/ordering.txt
+++ b/tools/memory-model/Documentation/ordering.txt
@@ -347,7 +347,7 @@ o Accessing RCU-protected pointers via rcu_dereference()
If there is any significant processing of the pointer value
between the rcu_dereference() that returned it and a later
- dereference(), please read Documentation/RCU/rcu_dereference.txt.
+ dereference(), please read Documentation/RCU/rcu_dereference.rst.
It can also be quite helpful to review uses in the Linux kernel.
--
2.26.2
reply other threads:[~2020-08-26 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200826104740.532184-1-mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--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
all inboxes | Powered by JetHome®