From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Chao Yu <chao@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] f2fs: Fix two spelling mistakes in f2fs_zone_status array
Date: Thu, 29 Feb 2024 09:12:01 -0800 [thread overview]
Message-ID: <ZeC64dDr-nBGlsli@google.com> (raw)
In-Reply-To: <20240229091449.105032-1-colin.i.king@gmail.com>
Hi Colin,
Thank you for the fix. If you don't mind, can I integrate this fix
into the original patch?
Thanks,
On 02/29, Colin Ian King wrote:
> The array f2fs_zone_status contains two spelling mistakes in
> literal strings. Fix them.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> fs/f2fs/segment.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index bdb27e4a604b..072c4355d3d3 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -4921,8 +4921,8 @@ static int sanity_check_curseg(struct f2fs_sb_info *sbi)
> const char *f2fs_zone_status[BLK_ZONE_COND_OFFLINE + 1] = {
> [BLK_ZONE_COND_NOT_WP] = "NOT_WP",
> [BLK_ZONE_COND_EMPTY] = "EMPTY",
> - [BLK_ZONE_COND_IMP_OPEN] = "IMPLICITE_OPEN",
> - [BLK_ZONE_COND_EXP_OPEN] = "EXPLICITE_OPEN",
> + [BLK_ZONE_COND_IMP_OPEN] = "IMPLICIT_OPEN",
> + [BLK_ZONE_COND_EXP_OPEN] = "EXPLICIT_OPEN",
> [BLK_ZONE_COND_CLOSED] = "CLOSED",
> [BLK_ZONE_COND_READONLY] = "READONLY",
> [BLK_ZONE_COND_FULL] = "FULL",
> --
> 2.39.2
next prev parent reply other threads:[~2024-02-29 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 9:14 [PATCH][next] f2fs: Fix two spelling mistakes in f2fs_zone_status array Colin Ian King
2024-02-29 17:12 ` Jaegeuk Kim [this message]
2024-02-29 17:22 ` Colin King (gmail)
2024-02-29 17:31 ` Jaegeuk Kim
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=ZeC64dDr-nBGlsli@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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