diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2023-05-23 22:51:01 +0200 |
---|---|---|
committer | Andrew Morton <akpm@linux-foundation.org> | 2023-08-18 10:12:00 -0700 |
commit | fad9c80e6371ee04a3fa5728efe20b88d8e4cccd (patch) | |
tree | 7b19d44f64d526eded6637af2a55dffaa026f4b5 /mm/mm_init.c | |
parent | 20c897eadf13ee4305af62dbdfe7819307ddf0bc (diff) | |
download | linux-fad9c80e6371ee04a3fa5728efe20b88d8e4cccd.tar.gz linux-fad9c80e6371ee04a3fa5728efe20b88d8e4cccd.tar.bz2 linux-fad9c80e6371ee04a3fa5728efe20b88d8e4cccd.zip |
maple_tree: fix a few documentation issues
The documentation of mt_next() claims that it starts the search at the
provided index. That's incorrect as it starts the search after the
provided index.
The documentation of mt_find() is slightly confusing. "Handles locking"
is not really helpful as it does not explain how the "locking" works.
Also the documentation of index talks about a range, while in reality the
index is updated on a succesful search to the index of the found entry
plus one.
Fix similar issues for mt_find_after() and mt_prev().
Reword the confusing "Note: Will not return the zero entry." comment on
mt_for_each() and document @__index correctly.
Link: https://lkml.kernel.org/r/87ttw2n556.ffs@tglx
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Shanker Donthineni <sdonthineni@nvidia.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/mm_init.c')
0 files changed, 0 insertions, 0 deletions