diff options
author | Rasmus Villemoes | 2014-08-06 16:10:14 -0700 |
---|---|---|
committer | Linus Torvalds | 2014-08-06 18:01:26 -0700 |
commit | a855174878f06d197ddfde5cbe1e69a1d4a2df27 (patch) | |
tree | 0f7e22266d90482753ab497d5691bfd3727ec76b | |
parent | bc5be1828065681300f3727ab55fac0d7ef37af3 (diff) |
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>
-rw-r--r-- | lib/bitmap.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/bitmap.c b/lib/bitmap.c index d4b3a6d4b2d7..2714df9f5cdb 100644 --- a/lib/bitmap.c +++ b/lib/bitmap.c @@ -712,7 +712,7 @@ EXPORT_SYMBOL(bitmap_parselist_user); * * 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. * |