From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@kernel.org, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-doc@vger.kernel.org, SeongJae Park <sjpark@amazon.de>
Subject: [PATCH v2 1/3] docs/memory-barriers.txt: Fix references for DMA*.txt files
Date: Sat, 29 Aug 2020 10:26:05 +0200 [thread overview]
Message-ID: <20200829082607.3146-2-sj38.park@gmail.com> (raw)
In-Reply-To: <20200829082607.3146-1-sj38.park@gmail.com>
From: SeongJae Park <sjpark@amazon.de>
Commit 985098a05eee ("docs: fix references for DMA*.txt files") missed
fixing memory-barriers.txt file. This commit applies the change to the
file.
Signed-off-by: SeongJae Park <sjpark@amazon.de>
---
Documentation/memory-barriers.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 96186332e5f4..17c8e0c2deb4 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -546,8 +546,8 @@ There are certain things that the Linux kernel memory barriers do not guarantee:
[*] For information on bus mastering DMA and coherency please read:
Documentation/driver-api/pci/pci.rst
- Documentation/DMA-API-HOWTO.txt
- Documentation/DMA-API.txt
+ Documentation/core-api/dma-api-howto.rst
+ Documentation/core-api/dma-api.rst
DATA DEPENDENCY BARRIERS (HISTORICAL)
@@ -1932,8 +1932,8 @@ There are some more advanced barrier functions:
here.
See the subsection "Kernel I/O barrier effects" for more information on
- relaxed I/O accessors and the Documentation/DMA-API.txt file for more
- information on consistent memory.
+ relaxed I/O accessors and the Documentation/core-api/dma-api.rst file for
+ more information on consistent memory.
(*) pmem_wmb();
--
2.17.1
next prev parent reply other threads:[~2020-08-29 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 8:26 [PATCH v2 0/3] docs/memory-barriers: Apply missed changes SeongJae Park
2020-08-29 8:26 ` SeongJae Park [this message]
2020-08-29 8:26 ` [PATCH v2 2/3] docs/memory-barriers.txt/kokr: Remove remaining references to mmiowb() SeongJae Park
2020-08-29 8:26 ` [PATCH v2 3/3] dics/memory-barriers.txt/kokr: Allow architecture to override the flush barrier SeongJae Park
2020-08-29 8:38 ` SeongJae Park
2020-08-29 8:40 ` [PATCH v3 3/3] docs/memory-barriers.txt/kokr: " SeongJae Park
2020-08-31 22:15 ` [PATCH v2 0/3] docs/memory-barriers: Apply missed changes 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=20200829082607.3146-2-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sjpark@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.