From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] f2fs: Remove unneeded semicolon
Date: Thu, 2 Feb 2023 13:37:40 -0800 [thread overview]
Message-ID: <Y9wtJLVjx9jmBxzZ@google.com> (raw)
In-Reply-To: <20230202010111.69078-1-yang.lee@linux.alibaba.com>
Thanks, but applied the fix in the original patch.
On 02/02, Yang Li wrote:
> ./fs/f2fs/checkpoint.c:1485:55-56: Unneeded semicolon
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=3925
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> fs/f2fs/checkpoint.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
> index b1b39c17f2d8..b7ef8cd10b10 100644
> --- a/fs/f2fs/checkpoint.c
> +++ b/fs/f2fs/checkpoint.c
> @@ -1482,7 +1482,7 @@ static int do_checkpoint(struct f2fs_sb_info *sbi, struct cp_control *cpc)
> for (i = 0; i < NR_CURSEG_DATA_TYPE; i++) {
> struct curseg_info *curseg = CURSEG_I(sbi, i + CURSEG_HOT_DATA);
>
> - ckpt->cur_data_segno[i] = cpu_to_le32(curseg->segno);;
> + ckpt->cur_data_segno[i] = cpu_to_le32(curseg->segno);
> ckpt->cur_data_blkoff[i] = cpu_to_le16(curseg->next_blkoff);
> ckpt->alloc_type[i + CURSEG_HOT_DATA] = curseg->alloc_type;
> }
> --
> 2.20.1.7.g153144c
prev parent reply other threads:[~2023-02-02 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 1:01 [PATCH -next] f2fs: Remove unneeded semicolon Yang Li
2023-02-02 21:37 ` Jaegeuk Kim [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=Y9wtJLVjx9jmBxzZ@google.com \
--to=jaegeuk@kernel.org \
--cc=abaci@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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