From: Qiujun Huang <hqjagain@gmail.com>
To: willy@infradead.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Qiujun Huang <hqjagain@gmail.com>
Subject: [PATCH 1/2] radix-tree: fix kernel-doc for radix_tree_find_next_bit
Date: Sat, 14 Mar 2020 02:49:08 +0800 [thread overview]
Message-ID: <20200313184909.4560-2-hqjagain@gmail.com> (raw)
In-Reply-To: <20200313184909.4560-1-hqjagain@gmail.com>
The function changed at some point, but the kernel-doc was
not updated.
Signed-off-by: Qiujun Huang <hqjagain@gmail.com>
---
lib/radix-tree.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/lib/radix-tree.c b/lib/radix-tree.c
index c8fa1d274530..379137875e25 100644
--- a/lib/radix-tree.c
+++ b/lib/radix-tree.c
@@ -178,12 +178,11 @@ static inline void all_tag_set(struct radix_tree_node *node, unsigned int tag)
* radix_tree_find_next_bit - find the next set bit in a memory region
*
* @addr: The address to base the search on
- * @size: The bitmap size in bits
+ * @tag: The tag index (< RADIX_TREE_MAX_TAGS)
* @offset: The bitnumber to start searching at
*
* Unrollable variant of find_next_bit() for constant size arrays.
- * Tail bits starting from size to roundup(size, BITS_PER_LONG) must be zero.
- * Returns next bit offset, or size if nothing found.
+ * Returns next bit offset, or RADIX_TREE_MAP_SIZE if nothing found.
*/
static __always_inline unsigned long
radix_tree_find_next_bit(struct radix_tree_node *node, unsigned int tag,
--
2.17.1
next prev parent reply other threads:[~2020-03-13 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 18:49 [PATCH 0/2] radix-tree: fix some errors in comment Qiujun Huang
2020-03-13 18:49 ` Qiujun Huang [this message]
2020-03-13 19:14 ` [PATCH 1/2] radix-tree: fix kernel-doc for radix_tree_find_next_bit Matthew Wilcox
2020-03-13 23:18 ` Qiujun Huang
2020-03-13 18:49 ` [PATCH 2/2] radix-tree: fix a typo Qiujun Huang
2020-03-13 19:12 ` Matthew Wilcox
2020-03-13 23:16 ` Qiujun Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200313184909.4560-2-hqjagain@gmail.com \
--to=hqjagain@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®