From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: josef@toxicpanda.com, Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/3] Simplify error handling in 3 functions
Date: Tue, 24 Nov 2020 17:49:29 +0200 [thread overview]
Message-ID: <20201124154932.3180539-1-nborisov@suse.com> (raw)
Here are 3 very similar patches which switch some functions from using 2
variables to implement their error handling to using simply 1 as the standard in
the codebase dictates.
Nikolay Borisov (3):
btrfs: Remove err variable from btrfs_delete_subvolume
btrfs: Eliminate err variable from merge_reloc_root
btrfs: Remove err variable from do_relocation
fs/btrfs/inode.c | 21 ++++++----------
fs/btrfs/relocation.c | 57 +++++++++++++++----------------------------
2 files changed, 26 insertions(+), 52 deletions(-)
--
2.25.1
next reply other threads:[~2020-11-24 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 15:49 Nikolay Borisov [this message]
2020-11-24 15:49 ` [PATCH 1/3] btrfs: Remove err variable from btrfs_delete_subvolume Nikolay Borisov
2020-11-24 15:49 ` [PATCH 2/3] btrfs: Eliminate err variable from merge_reloc_root Nikolay Borisov
2020-11-24 15:49 ` [PATCH 3/3] btrfs: Remove err variable from do_relocation Nikolay Borisov
2020-11-24 16:12 ` [PATCH 0/3] Simplify error handling in 3 functions 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=20201124154932.3180539-1-nborisov@suse.com \
--to=nborisov@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
/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