From: Hongbo Li <lihongbo22@huawei.com>
To: Chen Ni <nichen@iscas.ac.cn>, <kent.overstreet@linux.dev>,
<bfoster@redhat.com>
Cc: <linux-bcachefs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bcachefs: Convert comma to semicolon
Date: Tue, 16 Jul 2024 14:03:04 +0800 [thread overview]
Message-ID: <2335e293-9ef4-46ad-b1bd-4416dfeda604@huawei.com> (raw)
In-Reply-To: <20240716040302.684034-1-nichen@iscas.ac.cn>
On 2024/7/16 12:03, Chen Ni wrote:
> Replace a comma between expression statements by a semicolon.
>
> Fixes: 79032b078173 ("bcachefs: Improved topology repair checks")
> Signed-off-by: Chen Ni <nichen@iscas.ac.cn>
> ---
> fs/bcachefs/btree_update_interior.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/bcachefs/btree_update_interior.c b/fs/bcachefs/btree_update_interior.c
> index 31ee50184be2..51b43d75ddb6 100644
> --- a/fs/bcachefs/btree_update_interior.c
> +++ b/fs/bcachefs/btree_update_interior.c
> @@ -96,7 +96,7 @@ int bch2_btree_node_check_topology(struct btree_trans *trans, struct btree *b)
> bch2_topology_error(c);
>
> printbuf_reset(&buf);
> - prt_str(&buf, "end of prev node doesn't match start of next node\n"),
> + prt_str(&buf, "end of prev node doesn't match start of next node\n");
Reviewed-by: Hongbo Li <lihongbo22@huawei.com>
Thanks,
Hongbo
> prt_printf(&buf, " in btree %s level %u node ",
> bch2_btree_id_str(b->c.btree_id), b->c.level);
> bch2_bkey_val_to_text(&buf, c, bkey_i_to_s_c(&b->key));
next prev parent reply other threads:[~2024-07-16 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 4:03 [PATCH] bcachefs: Convert comma to semicolon Chen Ni
2024-07-16 6:03 ` Hongbo Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-14 2:10 Chen Ni
2025-07-29 1:36 Chen Ni
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=2335e293-9ef4-46ad-b1bd-4416dfeda604@huawei.com \
--to=lihongbo22@huawei.com \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nichen@iscas.ac.cn \
/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