From: Brian Foster <bfoster@redhat.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] bcachefs: Remove unneeded semicolon
Date: Wed, 13 Sep 2023 06:46:49 -0400 [thread overview]
Message-ID: <ZQGTGV0LRqkKBF6p@bfoster> (raw)
In-Reply-To: <20230913005756.6827-1-yang.lee@linux.alibaba.com>
On Wed, Sep 13, 2023 at 08:57:56AM +0800, Yang Li wrote:
> ./fs/bcachefs/btree_gc.c:1249:2-3: Unneeded semicolon
> ./fs/bcachefs/btree_gc.c:1521:2-3: Unneeded semicolon
> ./fs/bcachefs/btree_gc.c:1575:2-3: Unneeded semicolon
> ./fs/bcachefs/counters.c:46:2-3: Unneeded semicolon
>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
What produces these warnings? It would be help to add a sentence or two
of such context in the commit log.. even just a "XYZ reports the
following: ..."
Nit aside, patch seems fine to me:
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/bcachefs/btree_gc.c | 6 +++---
> fs/bcachefs/counters.c | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/fs/bcachefs/btree_gc.c b/fs/bcachefs/btree_gc.c
> index dac2eb76c985..56c671638c43 100644
> --- a/fs/bcachefs/btree_gc.c
> +++ b/fs/bcachefs/btree_gc.c
> @@ -1246,7 +1246,7 @@ static int bch2_gc_done(struct bch_fs *c,
> copy_dev_field(d[i].sectors, "%s sectors", bch2_data_types[i]);
> copy_dev_field(d[i].fragmented, "%s fragmented", bch2_data_types[i]);
> }
> - };
> + }
>
> {
> unsigned nr = fs_usage_u64s(c);
> @@ -1518,7 +1518,7 @@ static int bch2_gc_alloc_start(struct bch_fs *c, bool metadata_only)
> buckets->first_bucket = ca->mi.first_bucket;
> buckets->nbuckets = ca->mi.nbuckets;
> rcu_assign_pointer(ca->buckets_gc, buckets);
> - };
> + }
>
> bch2_trans_init(&trans, c, 0, 0);
>
> @@ -1572,7 +1572,7 @@ static void bch2_gc_alloc_reset(struct bch_fs *c, bool metadata_only)
> g->dirty_sectors = 0;
> g->cached_sectors = 0;
> }
> - };
> + }
> }
>
> static int bch2_gc_write_reflink_key(struct btree_trans *trans,
> diff --git a/fs/bcachefs/counters.c b/fs/bcachefs/counters.c
> index 442a9b806a3c..26eb3d82b1cb 100644
> --- a/fs/bcachefs/counters.c
> +++ b/fs/bcachefs/counters.c
> @@ -43,7 +43,7 @@ static void bch2_sb_counters_to_text(struct printbuf *out, struct bch_sb *sb,
> prt_tab(out);
> prt_printf(out, "%llu", le64_to_cpu(ctrs->d[i]));
> prt_newline(out);
> - };
> + }
> };
>
> int bch2_sb_counters_to_cpu(struct bch_fs *c)
> --
> 2.20.1.7.g153144c
>
next prev parent reply other threads:[~2023-09-13 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 0:57 [PATCH -next] bcachefs: Remove unneeded semicolon Yang Li
2023-09-13 10:46 ` Brian Foster [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 0:36 Yang Li
2023-11-22 0:43 Yang Li
2024-01-03 1:07 Yang Li
2024-09-10 0:49 Yang Li
2024-09-11 0:42 Yang Li
2024-11-07 1:10 Yang Li
2025-08-07 2:07 [PATCH -next] bcachefs: remove " Jiapeng Chong
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=ZQGTGV0LRqkKBF6p@bfoster \
--to=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yang.lee@linux.alibaba.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