From: kbuild test robot <lkp@intel.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org,
Omar Sandoval <osandov@osandov.com>
Subject: [PATCH] Btrfs: fix simple_return.cocci warnings
Date: Wed, 30 Sep 2015 12:35:45 +0800 [thread overview]
Message-ID: <20150930043545.GA11964@athens> (raw)
In-Reply-To: <3319d371e22491b6901af33842b57db37b77c52c.1443583874.git.osandov@osandov.com>
fs/btrfs/free-space-tree.c:1255:1-4: WARNING: end returns can be simpified
fs/btrfs/free-space-tree.c:1168:1-4: WARNING: end returns can be simpified
Simplify a trivial if-return sequence. Possibly combine with a
preceding function call.
Generated by: scripts/coccinelle/misc/simple_return.cocci
CC: Omar Sandoval <osandov@fb.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
free-space-tree.c | 12 ++----------
1 file changed, 2 insertions(+), 10 deletions(-)
--- a/fs/btrfs/free-space-tree.c
+++ b/fs/btrfs/free-space-tree.c
@@ -1165,11 +1165,7 @@ int btrfs_create_free_space_tree(struct
btrfs_set_fs_compat_ro(fs_info, FREE_SPACE_TREE);
- ret = btrfs_commit_transaction(trans, tree_root);
- if (ret)
- return ret;
-
- return 0;
+ return btrfs_commit_transaction(trans, tree_root);
abort:
btrfs_abort_transaction(trans, tree_root, ret);
@@ -1252,11 +1248,7 @@ int btrfs_clear_free_space_tree(struct b
free_extent_buffer(free_space_root->commit_root);
kfree(free_space_root);
- ret = btrfs_commit_transaction(trans, tree_root);
- if (ret)
- return ret;
-
- return 0;
+ return btrfs_commit_transaction(trans, tree_root);
abort:
btrfs_abort_transaction(trans, tree_root, ret);
next prev parent reply other threads:[~2015-09-30 4:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 3:50 [PATCH v4 0/9] Btrfs: free space B-tree Omar Sandoval
2015-09-30 3:50 ` [PATCH v4 1/9] Btrfs: add extent buffer bitmap operations Omar Sandoval
2015-09-30 3:50 ` [PATCH v4 2/9] Btrfs: add extent buffer bitmap sanity tests Omar Sandoval
2015-09-30 3:50 ` [PATCH v4 3/9] Btrfs: add helpers for read-only compat bits Omar Sandoval
2015-09-30 3:50 ` [PATCH v4 4/9] Btrfs: refactor caching_thread() Omar Sandoval
2015-09-30 3:50 ` [PATCH v4 5/9] Btrfs: introduce the free space B-tree on-disk format Omar Sandoval
2015-09-30 3:50 ` [PATCH v4 6/9] Btrfs: implement the free space B-tree Omar Sandoval
2015-09-30 4:35 ` kbuild test robot
2015-09-30 4:35 ` kbuild test robot [this message]
2015-10-01 12:54 ` David Sterba
2015-10-02 14:23 ` kbuild test robot
2015-12-29 20:19 ` Chris Mason
2016-04-22 8:28 ` Alex Lyakas
2016-05-02 21:55 ` Omar Sandoval
2015-09-30 3:50 ` [PATCH v4 7/9] Btrfs: add free space tree sanity tests Omar Sandoval
2015-10-01 13:04 ` David Sterba
2023-10-11 2:12 ` Jinjie Ruan
2023-10-11 10:20 ` David Sterba
2015-09-30 3:50 ` [PATCH v4 8/9] Btrfs: wire up the free space tree to the extent tree Omar Sandoval
2015-09-30 3:50 ` [PATCH v4 9/9] Btrfs: add free space tree mount option Omar Sandoval
2015-09-30 3:51 ` [PATCH v4 1/2] btrfs-progs: add basic awareness of the free space tree Omar Sandoval
2015-09-30 3:51 ` [PATCH v4 2/2] btrfs-progs: check the free space tree in btrfsck Omar Sandoval
2015-09-30 8:31 ` [PATCH v4 0/9] Btrfs: free space B-tree Omar Sandoval
2015-10-02 11:47 ` Austin S Hemmelgarn
2015-11-03 18:13 ` Tobias Holst
2015-11-03 18:34 ` Chris Mason
2015-11-03 18:59 ` Tobias Holst
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=20150930043545.GA11964@athens \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.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;
as well as URLs for NNTP newsgroup(s).