[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5e705d83-871e-4403-a77f-ec197eefb7c4@gmail.com>
Date: Thu, 29 Feb 2024 17:22:54 +0000
From: "Colin King (gmail)" <colin.i.king@...il.com>
To: Jaegeuk Kim <jaegeuk@...nel.org>
Cc: Chao Yu <chao@...nel.org>, linux-f2fs-devel@...ts.sourceforge.net,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] f2fs: Fix two spelling mistakes in f2fs_zone_status
array
On 29/02/2024 17:12, Jaegeuk Kim wrote:
> Hi Colin,
>
> Thank you for the fix. If you don't mind, can I integrate this fix
> into the original patch?
Sure. No problem.
Colin
>
> 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@...il.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
Powered by blists - more mailing lists