From: Burenchev Evgenii <EBurenchev@orionsoft.ru>
To: "dsterba@suse.cz" <dsterba@suse.cz>
Cc: "clm@fb.com" <clm@fb.com>, "dsterba@suse.com" <dsterba@suse.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
"mssola@mssola.com" <mssola@mssola.com>,
"fdmanana@kernel.org" <fdmanana@kernel.org>
Subject: [PATCH v2 2/2] btrfs: initialize ret at declaration and remove redundant assignment
Date: Wed, 25 Feb 2026 12:41:05 +0000 [thread overview]
Message-ID: <2ef0d6ce96e44f2ab92c5dacdff4f597@orionsoft.ru> (raw)
Related discussion: https://lore.kernel.org/linux-btrfs/20260224172835.GB26902@twin.jikos.cz
Initialize ret at declaration and remove a redundant
"ret = 0" before the out: label.
This matches the usual return value handling pattern used in
similar functions.
No functional change.
Changes since v1:
- split from original patch
Signed-off-by: Evgenii Burenchev <eburenchev@orionsoft.ru>
---
fs/btrfs/ioctl.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index 3a45ee1a7026..de59eacc33b4 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -1647,7 +1647,7 @@ static noinline int btrfs_search_path_in_tree(struct btrfs_fs_info *info,
struct btrfs_root *root;
struct btrfs_key key;
char *ptr;
- int ret = -1;
+ int ret = 0;
int slot;
int len;
int total_len = 0;
@@ -1710,7 +1710,6 @@ static noinline int btrfs_search_path_in_tree(struct btrfs_fs_info *info,
}
memmove(name, ptr, total_len);
name[total_len] = '\0';
- ret = 0;
out:
btrfs_put_root(root);
return ret;
--
2.43.0
reply other threads:[~2026-02-25 12:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2ef0d6ce96e44f2ab92c5dacdff4f597@orionsoft.ru \
--to=eburenchev@orionsoft.ru \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mssola@mssola.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