lib: bitmap: fix typo in kerneldoc for bitmap_pos_to_ord

A few lines above, it was stated that positions for non-set bits are mapped to -1, which is obviously also what the code does. Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

lib: bitmap: fix typo in kerneldoc for bitmap_pos_to_ord
A few lines above, it was stated that positions for non-set bits are mapped to -1, which is obviously also what the code does. Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Rasmus Villemoes · Linus Torvalds
1 parent bc5be18280
Showing 1 changed file with 1 additions and 1 deletions Side-by-side Diff
lib/bitmap.c
@@ -712,7 +712,7 @@
  *
  * If for example, just bits 4 through 7 are set in @buf, then @pos
  * values 4 through 7 will get mapped to 0 through 3, respectively,
- * and other @pos values will get mapped to 0.  When @pos value 7
+ * and other @pos values will get mapped to -1.  When @pos value 7
  * gets mapped to (returns) @ord value 3 in this example, that means
  * that bit 7 is the 3rd (starting with 0th) set bit in @buf.
  *
...	...	@@ -712,7 +712,7 @@
712	712	*
713	713	* If for example, just bits 4 through 7 are set in @buf, then @pos
714	714	* values 4 through 7 will get mapped to 0 through 3, respectively,
715		- * and other @pos values will get mapped to 0. When @pos value 7
	715	+ * and other @pos values will get mapped to -1. When @pos value 7
716	716	* gets mapped to (returns) @ord value 3 in this example, that means
717	717	* that bit 7 is the 3rd (starting with 0th) set bit in @buf.
718	718	*