From: Matthew Wilcox <willy@infradead.org>
To: wuchi <wuchi.zero@gmail.com>
Cc: rdunlap@infradead.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/radix-tree: Remove unuse argument of insert_entries
Date: Fri, 24 Jun 2022 17:56:05 +0100 [thread overview]
Message-ID: <YrXspV63H5Wuyd/j@casper.infradead.org> (raw)
In-Reply-To: <20220624131523.46153-1-wuchi.zero@gmail.com>
On Fri, Jun 24, 2022 at 09:15:23PM +0800, wuchi wrote:
> Function insert_entries doesn't use the 'bool replace' argument,
> and the function is only used locally, remove the argument.
Thanks. For these kinds of patches, I like the changelog to contain the
historical context for when the code changed to make this argument unused.
Can you add that?
> Signed-off-by: wuchi <wuchi.zero@gmail.com>
> ---
> lib/radix-tree.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/radix-tree.c b/lib/radix-tree.c
> index b3afafe46fff..3c78e1e8b2ad 100644
> --- a/lib/radix-tree.c
> +++ b/lib/radix-tree.c
> @@ -677,7 +677,7 @@ static void radix_tree_free_nodes(struct radix_tree_node *node)
> }
>
> static inline int insert_entries(struct radix_tree_node *node,
> - void __rcu **slot, void *item, bool replace)
> + void __rcu **slot, void *item)
> {
> if (*slot)
> return -EEXIST;
> @@ -711,7 +711,7 @@ int radix_tree_insert(struct radix_tree_root *root, unsigned long index,
> if (error)
> return error;
>
> - error = insert_entries(node, slot, item, false);
> + error = insert_entries(node, slot, item);
> if (error < 0)
> return error;
>
> --
> 2.20.1
>
prev parent reply other threads:[~2022-06-24 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 13:15 wuchi
2022-06-24 16:56 ` Matthew Wilcox [this message]
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=YrXspV63H5Wuyd/j@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=wuchi.zero@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
all inboxes | Powered by JetHome®