Received-SPF: pass (google.com: domain of linux-kernel+bounces-87149-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Thu, 29 Feb 2024 09:12:01 -0800
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
Message-ID: <ZeC64dDr-nBGlsli@google.com>
References: <20240229091449.105032-1-colin.i.king@gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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