mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: cgel.zte@gmail.com, clm@fb.com
Cc: josef@toxicpanda.com, dsterba@suse.com,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Changcheng Deng <deng.changcheng@zte.com.cn>,
	Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] btrfs: remove unneeded variable
Date: Fri, 17 Dec 2021 18:14:25 +0800	[thread overview]
Message-ID: <69c7ac46-a469-d4d2-d4a7-c45f722816a0@gmx.com> (raw)
In-Reply-To: <20211217084522.452493-1-deng.changcheng@zte.com.cn>



On 2021/12/17 16:45, cgel.zte@gmail.com wrote:
> From: Changcheng Deng <deng.changcheng@zte.com.cn>
>
> Remove unneeded variable used to store return value.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Changcheng Deng <deng.changcheng@zte.com.cn>
> ---
>   fs/btrfs/disk-io.c | 5 ++---
>   1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index d94a1ca856aa..d33575e56da2 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -4658,7 +4658,6 @@ static int btrfs_destroy_delayed_refs(struct btrfs_transaction *trans,
>   	struct rb_node *node;
>   	struct btrfs_delayed_ref_root *delayed_refs;
>   	struct btrfs_delayed_ref_node *ref;
> -	int ret = 0;

If you're removing @ret, it's better to also change the return value to
void.

Normally I would suggest you to checker the caller and return proper
error number instead.

But in this particular case, this function is only called in transaction
cleanup code, which means we have already aborted a transaction, thus
there is not much meaning to further error out, and the cleanup is OK.


So it would be fine for you to delete @ret, change the function to
return void.
And even better, to remove the "btrfs_" prefix of the function, as the
function is not really exported.


And a final suggest for your future patches, there is no need to bother
btrfs maintainers at all, just sending the mail to btrfs mailing list is
enough.

Thanks,
Qu
>
>   	delayed_refs = &trans->delayed_refs;
>
> @@ -4666,7 +4665,7 @@ static int btrfs_destroy_delayed_refs(struct btrfs_transaction *trans,
>   	if (atomic_read(&delayed_refs->num_entries) == 0) {
>   		spin_unlock(&delayed_refs->lock);
>   		btrfs_debug(fs_info, "delayed_refs has NO entry");
> -		return ret;
> +		return 0;
>   	}
>
>   	while ((node = rb_first_cached(&delayed_refs->href_root)) != NULL) {
> @@ -4729,7 +4728,7 @@ static int btrfs_destroy_delayed_refs(struct btrfs_transaction *trans,
>
>   	spin_unlock(&delayed_refs->lock);
>
> -	return ret;
> +	return 0;
>   }
>
>   static void btrfs_destroy_delalloc_inodes(struct btrfs_root *root)

  reply	other threads:[~2021-12-17 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  8:45 cgel.zte
2021-12-17 10:14 ` Qu Wenruo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-10 11:56 cgel.zte
2021-11-10 15:20 ` David Sterba

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=69c7ac46-a469-d4d2-d4a7-c45f722816a0@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=cgel.zte@gmail.com \
    --cc=clm@fb.com \
    --cc=deng.changcheng@zte.com.cn \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zealci@zte.com.cn \
    /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®