From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Adarsh Das <adarshdas950@gmail.com>, clm@fb.com, dsterba@suse.com
Cc: terrelln@fb.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] btrfs: clean coding style errors in extent-tree.c
Date: Sat, 28 Feb 2026 07:14:21 +1030 [thread overview]
Message-ID: <24efa2ba-44c7-472e-adbb-60f2e0200ba9@gmx.com> (raw)
In-Reply-To: <20260227183111.9311-5-adarshdas950@gmail.com>
在 2026/2/28 05:01, Adarsh Das 写道:
> As the previous commits are changing code in extent-tree, this patch
> takes the oppurtunity to fix checkpatch errors in the same files. All
> the errors were formatting related.
>
> Signed-off-by: Adarsh Das <adarshdas950@gmail.com>
Just fold this into the previous patch.
Thanks,
Qu
> ---
> fs/btrfs/extent-tree.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 9748a4c5bc2d..8ea88174e4d5 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -2111,7 +2111,7 @@ static noinline int __btrfs_run_delayed_refs(struct btrfs_trans_handle *trans,
> * head
> */
> ret = cleanup_ref_head(trans, locked_ref, &bytes_processed);
> - if (ret > 0 ) {
> + if (ret > 0) {
> /* We dropped our lock, we need to loop. */
> ret = 0;
> continue;
> @@ -4351,8 +4351,7 @@ static int find_free_extent_update_loop(struct btrfs_fs_info *fs_info,
> if (ret == -ENOSPC) {
> ret = 0;
> ffe_ctl->loop++;
> - }
> - else if (ret < 0)
> + } else if (ret < 0)
> btrfs_abort_transaction(trans, ret);
> else
> ret = 0;
> @@ -5676,7 +5675,7 @@ static int check_ref_exists(struct btrfs_trans_handle *trans,
> * If we get 0 then we found our reference, return 1, else
> * return the error if it's not -ENOENT;
> */
> - return (ret < 0 ) ? ret : 1;
> + return (ret < 0) ? ret : 1;
> }
>
> /*
next prev parent reply other threads:[~2026-02-27 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 18:31 [PATCH 0/4] btrfs: replace BUG() and BUG_ON() with error handling Adarsh Das
2026-02-27 18:31 ` [PATCH 1/4] btrfs: replace BUG() with error handling in compression.c Adarsh Das
2026-02-27 20:22 ` Qu Wenruo
2026-02-27 18:31 ` [PATCH 2/4] btrfs: clean coding style errors and warnings " Adarsh Das
2026-02-27 20:43 ` Qu Wenruo
2026-02-27 18:31 ` [PATCH 3/4] btrfs: replace BUG() and BUG_ON() with error handling in extent-tree.c Adarsh Das
2026-02-27 20:43 ` Qu Wenruo
2026-02-27 18:31 ` [PATCH 4/4] btrfs: clean coding style errors " Adarsh Das
2026-02-27 20:44 ` Qu Wenruo [this message]
2026-02-27 21:01 ` [PATCH 0/4] btrfs: replace BUG() and BUG_ON() with error handling Qu Wenruo
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=24efa2ba-44c7-472e-adbb-60f2e0200ba9@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=adarshdas950@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrelln@fb.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