From: SeongJae Park <sj@kernel.org>
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: SeongJae Park <sj@kernel.org>, Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@meta.com
Subject: Re: [PATCH] mm/nodemask: Correctly describe nodemask operation return types
Date: Fri, 29 May 2026 17:27:48 -0700 [thread overview]
Message-ID: <20260530002749.87977-1-sj@kernel.org> (raw)
In-Reply-To: <20260529202755.1846800-1-joshua.hahnjy@gmail.com>
On Fri, 29 May 2026 13:27:54 -0700 Joshua Hahn <joshua.hahnjy@gmail.com> wrote:
> Commit 0dfe54071d7c8 ("nodemask: Fix return values to be unsigned")
> changed a number of nodemask operations that used to return int
> to returning a bool instead. However, it did not update the comment
> block that described these functions, leaving the documentation
> incorrect.
>
> Fix the comment block to accurately describe the functions.
> Also fix a typo (unsigend --> unsigned), and fix a callsite in
> mempolicy.c that did not get updated during the conversion.
Nice catch, thank you fixing this!
>
> No functional changes intended; changes are purely cosmetic.
>
> Signed-off-by: Joshua Hahn <joshua.hahnjy@gmail.com>
Reviewed-by: SeongJae Park <sj@kernel.org>
> ---
> include/linux/nodemask.h | 18 +++++++++---------
> mm/mempolicy.c | 2 +-
> 2 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/include/linux/nodemask.h b/include/linux/nodemask.h
> index 204c92462f3c0..b842aa5255464 100644
> --- a/include/linux/nodemask.h
> +++ b/include/linux/nodemask.h
> @@ -24,23 +24,23 @@
> * void nodes_setall(mask) set all bits
> * void nodes_clear(mask) clear all bits
> * int node_isset(node, mask) true iff bit 'node' set in mask
> - * int node_test_and_set(node, mask) test and set bit 'node' in mask
> + * bool node_test_and_set(node, mask) test and set bit 'node' in mask
> *
> - * void nodes_and(dst, src1, src2) dst = src1 & src2 [intersection]
> + * bool nodes_and(dst, src1, src2) dst = src1 & src2 [intersection]
> * void nodes_or(dst, src1, src2) dst = src1 | src2 [union]
> * void nodes_xor(dst, src1, src2) dst = src1 ^ src2
> - * void nodes_andnot(dst, src1, src2) dst = src1 & ~src2
> + * bool nodes_andnot(dst, src1, src2) dst = src1 & ~src2
> * void nodes_complement(dst, src) dst = ~src
> *
> - * int nodes_equal(mask1, mask2) Does mask1 == mask2?
> - * int nodes_intersects(mask1, mask2) Do mask1 and mask2 intersect?
> - * int nodes_subset(mask1, mask2) Is mask1 a subset of mask2?
> - * int nodes_empty(mask) Is mask empty (no bits sets)?
> - * int nodes_full(mask) Is mask full (all bits sets)?
> + * bool nodes_equal(mask1, mask2) Does mask1 == mask2?
> + * bool nodes_intersects(mask1, mask2) Do mask1 and mask2 intersect?
> + * bool nodes_subset(mask1, mask2) Is mask1 a subset of mask2?
> + * bool nodes_empty(mask) Is mask empty (no bits sets)?
> + * bool nodes_full(mask) Is mask full (all bits sets)?
> * int nodes_weight(mask) Hamming weight - number of set bits
> *
> * unsigned int first_node(mask) Number lowest set bit, or MAX_NUMNODES
> - * unsigend int next_node(node, mask) Next node past 'node', or MAX_NUMNODES
> + * unsigned int next_node(node, mask) Next node past 'node', or MAX_NUMNODES
> * unsigned int next_node_in(node, mask) Next node past 'node', or wrap to first,
> * or MAX_NUMNODES
> * unsigned int first_unset_node(mask) First node not set in mask, or
I feel like this comment block might be easy to be outdated in future. This
comment block is introduced before the git era. I think this was the best and
great way at that time. But now we have modern documentation tools like
kernel-doc. I'm wondering if it makes sense to convert this comment block to
kernel-doc comments in long term, after this patch is merged. If we sure these
APIs are quite stable and expect no many changes in future, such conversion may
not make sense, though.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-05-30 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 20:27 Joshua Hahn
2026-05-30 0:27 ` SeongJae Park [this message]
2026-06-01 14:42 ` Joshua Hahn
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=20260530002749.87977-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@rasmusvillemoes.dk \
--cc=yury.norov@gmail.com \
/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
Powered by JetHome