Re: [PATCH] fanotify: Fix spelling mistake "enforecement" -> "enforcement"

On Sat 18-04-26 20:42:30, Ethan Carter Edwards wrote:
> There is a spelling mistake in a comment. Fix it.
> 
> Signed-off-by: Ethan Carter Edwards <[email protected]>

Thanks. Patch queued up.

								Honza

> ---
>  fs/notify/fanotify/fanotify.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c
> index bfe884d624e7..38290b9c07f7 100644
> --- a/fs/notify/fanotify/fanotify.c
> +++ b/fs/notify/fanotify/fanotify.c
> @@ -457,7 +457,7 @@ static int fanotify_encode_fh(struct fanotify_fh *fh, struct inode *inode,
>  	/*
>  	 * Unlike file_handle, type and len of struct fanotify_fh are u8.
>  	 * Traditionally, filesystem return handle_type < 0xff, but there
> -	 * is no enforecement for that in vfs.
> +	 * is no enforcement for that in vfs.
>  	 */
>  	BUILD_BUG_ON(MAX_HANDLE_SZ > 0xff || FILEID_INVALID > 0xff);
>  	if (type <= 0 || type >= FILEID_INVALID || fh_len != dwords << 2)
> 
> ---
> base-commit: c7275b05bc428c7373d97aa2da02d3a7fa6b9f66
> change-id: 20260418-fanotify-typo-c4ec2ad325f0
> 
> Best regards,
> -- 
> Ethan Carter Edwards <[email protected]>
> 
-- 
Jan Kara <[email protected]>
SUSE Labs, CR