Re: [PATCH 6/6] zonefs: fix "writen"->"written"

[Damien Le Moal <dlemoal@kernel.org>]

On 8/8/25 4:14 PM, Xichao Zhao wrote:
> Trivial fix to spelling mistake in comment text.
> 
> Signed-off-by: Xichao Zhao <zhao.xichao@vivo.com>

Please squash this with patch 5/6. There is no good reason to have 2 patches
for typo fixes.

Also split this into separate patches for each FS. The entire patch series is
not going to be applied in a single tree. The different FS maintainers wil (or
not) take the patches for their FS in their tree.

> ---
>  fs/zonefs/super.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
> index 4dc7f967c861..70be0b3dda49 100644
> --- a/fs/zonefs/super.c
> +++ b/fs/zonefs/super.c
> @@ -268,7 +268,7 @@ static void zonefs_handle_io_error(struct inode *inode, struct blk_zone *zone,
>  	 * Check the zone condition: if the zone is not "bad" (offline or
>  	 * read-only), read errors are simply signaled to the IO issuer as long
>  	 * as there is no inconsistency between the inode size and the amount of
> -	 * data writen in the zone (data_size).
> +	 * data written in the zone (data_size).
>  	 */
>  	data_size = zonefs_check_zone_condition(sb, z, zone);
>  	isize = i_size_read(inode);
> @@ -282,7 +282,7 @@ static void zonefs_handle_io_error(struct inode *inode, struct blk_zone *zone,
>  	 * For the latter case, the cause may be a write IO error or an external
>  	 * action on the device. Two error patterns exist:
>  	 * 1) The inode size is lower than the amount of data in the zone:
> -	 *    a write operation partially failed and data was writen at the end
> +	 *    a write operation partially failed and data was written at the end
>  	 *    of the file. This can happen in the case of a large direct IO
>  	 *    needing several BIOs and/or write requests to be processed.
>  	 * 2) The inode size is larger than the amount of data in the zone:


-- 
Damien Le Moal
Western Digital Research