lkml.org 
[lkml]   [2021]   [May]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Subject[PATCH] docs: core-api: cachetlb: Fix up invalidate_kernel_vmap_range()
Date
From
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
\
 
 \ /
  Last update: 2021-05-16 07:58    [W:0.034 / U:0.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site