From: Palmer Dabbelt <palmer@dabbelt.com>
To: corbet@lwn.net
Cc: akpm@linux-foundation.org, npiggin@gmail.com,
Palmer Dabbelt <palmerdabbelt@google.com>,
peterz@infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [PATCH] docs: core-api: cachetlb: Fix up invalidate_kernel_vmap_range()
Date: Sat, 15 May 2021 22:56:01 -0700 [thread overview]
Message-ID: <20210516055601.2819-1-palmer@dabbelt.com> (raw)
From: Palmer Dabbelt <palmerdabbelt@google.com>
The first word of the function description ended up inside the function
prototype, likely during an ReST conversion. I've fixed that up, the diff
looks big because I re-wrapped the whole paragraph.
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
---
Documentation/core-api/cachetlb.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/core-api/cachetlb.rst b/Documentation/core-api/cachetlb.rst
index fe4290e26729..548ae069ed9e 100644
--- a/Documentation/core-api/cachetlb.rst
+++ b/Documentation/core-api/cachetlb.rst
@@ -396,10 +396,10 @@ I/O and invalidating it after the I/O returns.
Note that this API does *not* also flush the offset map alias
of the area.
- ``void invalidate_kernel_vmap_range(void *vaddr, int size) invalidates``
+ ``void invalidate_kernel_vmap_range(void *vaddr, int size)``
- the cache for a given virtual address range in the vmap area
- which prevents the processor from making the cache stale by
- speculatively reading data while the I/O was occurring to the
- physical pages. This is only necessary for data reads into the
- vmap area.
+ invalidates the cache for a given virtual address range in the
+ vmap area which prevents the processor from making the cache
+ stale by speculatively reading data while the I/O was occurring
+ to the physical pages. This is only necessary for data reads
+ into the vmap area.
--
2.20.1
reply other threads:[~2021-05-16 5:57 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=20210516055601.2819-1-palmer@dabbelt.com \
--to=palmer@dabbelt.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=palmerdabbelt@google.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).