Skip to content

Commit 01a7eb3

Browse files
Matthew Wilcox (Oracle)akpm00
authored andcommitted
mm: fix clean_record_shared_mapping_range kernel-doc
Turn the a), b) into an unordered ReST list and remove the unnecessary 'Note:' prefix. Link: https://lkml.kernel.org/r/20230818200630.2719595-4-willy@infradead.org Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Acked-by: Mike Rapoport (IBM) <rppt@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
1 parent 853f62a commit 01a7eb3

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

mm/mapping_dirty_helpers.c

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -288,13 +288,14 @@ EXPORT_SYMBOL_GPL(wp_shared_mapping_range);
288288
* @end: Pointer to the number of the last set bit in @bitmap.
289289
* none set. The value is modified as new bits are set by the function.
290290
*
291-
* Note: When this function returns there is no guarantee that a CPU has
291+
* When this function returns there is no guarantee that a CPU has
292292
* not already dirtied new ptes. However it will not clean any ptes not
293293
* reported in the bitmap. The guarantees are as follows:
294-
* a) All ptes dirty when the function starts executing will end up recorded
295-
* in the bitmap.
296-
* b) All ptes dirtied after that will either remain dirty, be recorded in the
297-
* bitmap or both.
294+
*
295+
* * All ptes dirty when the function starts executing will end up recorded
296+
* in the bitmap.
297+
* * All ptes dirtied after that will either remain dirty, be recorded in the
298+
* bitmap or both.
298299
*
299300
* If a caller needs to make sure all dirty ptes are picked up and none
300301
* additional are added, it first needs to write-protect the address-space

0 commit comments

Comments
 (0)