From: David Sterba <dsterba@suse.cz>
To: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/5] btrfs: remove a useless return statement in btrfs_block_rsv_add
Date: Fri, 17 Aug 2018 15:29:59 +0200 [thread overview]
Message-ID: <20180817132957.GU24025@twin.jikos.cz> (raw)
In-Reply-To: <20180804131057.9967-5-lufq.fnst@cn.fujitsu.com>
On Sat, Aug 04, 2018 at 09:10:56PM +0800, Lu Fengqi wrote:
> Since ret must be 0 here, don't have to return separately in advance.
>
> No functional change.
>
> Signed-off-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Added to misc-next too, the change is fairly trivial so I was pondering
about code readability impacts, but it's ok.
next prev parent reply other threads:[~2018-08-17 16:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 13:10 [PATCH 0/5] some trivial cleanup about btrfs_delete_subvolume Lu Fengqi
2018-08-04 13:10 ` [PATCH 1/5] btrfs: simplify the send_in_progress check in btrfs_delete_subvolume() Lu Fengqi
2018-08-07 16:03 ` David Sterba
2018-08-04 13:10 ` [PATCH 2/5] btrfs: use a separate variable to store the num_bytes of the qgroup_reserve Lu Fengqi
2018-08-04 13:54 ` [PATCH v2 " Lu Fengqi
2018-08-07 16:19 ` [PATCH " David Sterba
2018-08-08 3:04 ` Lu Fengqi
2018-08-08 13:56 ` David Sterba
2018-08-08 14:33 ` Lu Fengqi
2018-08-08 3:48 ` Gu, Jinxiang
2018-08-04 13:10 ` [PATCH 3/5] btrfs: switch update_size to bool in both of btrfs_block_rsv_migrate and btrfs_rsv_add_bytes Lu Fengqi
2018-08-07 16:02 ` David Sterba
2018-08-04 13:10 ` [PATCH 4/5] btrfs: remove a useless return statement in btrfs_block_rsv_add Lu Fengqi
2018-08-17 13:29 ` David Sterba [this message]
2018-08-04 13:10 ` [PATCH 5/5] btrfs: Remove root parameter from btrfs_insert_dir_item Lu Fengqi
2018-08-07 16:01 ` 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=20180817132957.GU24025@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.