From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>, clm@fb.com
Cc: josef@toxicpanda.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] btrfs: clean up some inconsistent indenting
Date: Thu, 7 Mar 2024 18:23:34 +1030 [thread overview]
Message-ID: <40b4f295-5539-406e-ba63-384685cb482c@gmx.com> (raw)
In-Reply-To: <20240307064753.36780-1-jiapeng.chong@linux.alibaba.com>
在 2024/3/7 17:17, Jiapeng Chong 写道:
> No functional modification involved.
>
> fs/btrfs/volumes.c:770 device_list_add() warn: inconsistent indenting.
> fs/btrfs/volumes.c:1373 btrfs_scan_one_device() warn: inconsistent indenting.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=8453
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Can the bot be taught to watch the btrfs development branch
(https://github.com/btrfs/linux.git for-next) and send feedback directly
to the btrfs mailing list?
So that we can catch the problem immediately before reaching mainline.
I strongly doubt sending out such patches would leave any positive
impression on the bot.
Thanks,
Qu
> ---
> fs/btrfs/volumes.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index a2d07fa3cfdf..caa3e83b0d6c 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -767,7 +767,7 @@ static noinline struct btrfs_device *device_list_add(const char *path,
> if (same_fsid_diff_dev) {
> generate_random_uuid(fs_devices->fsid);
> fs_devices->temp_fsid = true;
> - pr_info("BTRFS: device %s (%d:%d) using temp-fsid %pU\n",
> + pr_info("BTRFS: device %s (%d:%d) using temp-fsid %pU\n",
> path, MAJOR(path_devt), MINOR(path_devt),
> fs_devices->fsid);
> }
> @@ -1370,8 +1370,9 @@ struct btrfs_device *btrfs_scan_one_device(const char *path, blk_mode_t flags,
> else
> btrfs_free_stale_devices(devt, NULL);
>
> - pr_debug("BTRFS: skip registering single non-seed device %s (%d:%d)\n",
> - path, MAJOR(devt), MINOR(devt));
> + pr_debug("BTRFS: skip registering single non-seed device %s (%d:%d)\n",
> + path, MAJOR(devt), MINOR(devt));
> +
> device = NULL;
> goto free_disk_super;
> }
prev parent reply other threads:[~2024-03-07 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 6:47 [PATCH] btrfs: clean up some inconsistent indenting Jiapeng Chong
2024-03-07 7:53 ` Qu Wenruo [this message]
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=40b4f295-5539-406e-ba63-384685cb482c@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=abaci@linux.alibaba.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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