From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 14/35] maple_tree: Reorganize kerneldoc parameter names
Date: Tue, 8 Oct 2024 20:27:00 -0400 [thread overview]
Message-ID: <o3bmzzj22wquh24g6hnlbw3anqk5ykxgjlhtzu5oy35sd6p7vq@kpwd6llxgiau> (raw)
In-Reply-To: <20240930112121.95324-15-Julia.Lawall@inria.fr>
* Julia Lawall <Julia.Lawall@inria.fr> [240930 07:21]:
> Reorganize kerneldoc parameter names to match the parameter
> order in the function header.
>
> Problems identified using Coccinelle.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
Reviewed-by: Liam R. Howlett <Liam.Howlett@Oracle.com>
>
> ---
> lib/maple_tree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/maple_tree.c b/lib/maple_tree.c
> index 37abf0fe380b..b7f59c40530e 100644
> --- a/lib/maple_tree.c
> +++ b/lib/maple_tree.c
> @@ -4327,9 +4327,9 @@ static inline void *mas_insert(struct ma_state *mas, void *entry)
> * mas_alloc_cyclic() - Internal call to find somewhere to store an entry
> * @mas: The maple state.
> * @startp: Pointer to ID.
> + * @entry: The entry to store.
> * @range_lo: Lower bound of range to search.
> * @range_hi: Upper bound of range to search.
> - * @entry: The entry to store.
> * @next: Pointer to next ID to allocate.
> * @gfp: The GFP_FLAGS to use for allocations.
> *
>
>
next prev parent reply other threads:[~2024-10-09 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 11:20 [PATCH 00/35] " Julia Lawall
2024-09-30 11:21 ` [PATCH 14/35] maple_tree: " Julia Lawall
2024-10-09 0:27 ` Liam R. Howlett [this message]
2024-09-30 11:21 ` [PATCH 32/35] mm/mmu_notifiers: " Julia Lawall
2024-10-06 1:55 ` (subset) [PATCH 00/35] " Bjorn Andersson
2024-11-17 12:09 ` Michael Ellerman
2024-12-20 17:27 ` Srinivas Kandagatla
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=o3bmzzj22wquh24g6hnlbw3anqk5ykxgjlhtzu5oy35sd6p7vq@kpwd6llxgiau \
--to=liam.howlett@oracle.com \
--cc=Julia.Lawall@inria.fr \
--cc=akpm@linux-foundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.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