Re: [PATCH] include: linux: Fix a typo in the file fs.h

[Bhaskar Chowdhury]

On 23:06 Fri 12 Mar 2021, Tom Saeger wrote:
> On Sat, Mar 13, 2021 at 10:49:55AM +0530, Bhaskar Chowdhury wrote:
> > s/varous/various/
> >
> > Signed-off-by: Bhaskar Chowdhury <unixbhaskar@xxxxxxxxx>
> > ---
> >  include/linux/fs.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > index ec8f3ddf4a6a..c37a17c32d74 100644
> > --- a/include/linux/fs.h
> > +++ b/include/linux/fs.h
> > @@ -1051,7 +1051,7 @@ bool opens_in_grace(struct net *);
> >   * FIXME: should we create a separate "struct lock_request" to help distinguish
> >   * these two uses?
> >   *
> > - * The varous i_flctx lists are ordered by:
> > + * The various i_flctx lists are ordered by:
> >   *
> >   * 1) lock owner
> >   * 2) lock range start
> > --
> > 2.26.2
>
> How about a few more?
>
> found by running:
> codespell -w -i 3 include/linux/fs.h
Never bother to use that tool...not sure ...

> 'specialy' could be 'special' or 'specialty'
> it can be dropped altogether IMO, so I did.
>
> --Tom
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index c37a17c32d74..9ffea695a059 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -126,7 +126,7 @@ typedef int (dio_iodone_t)(struct kiocb *iocb, loff_t offset,
> /* File is opened with O_EXCL (only set for block devices) */
> #define FMODE_EXCL             ((__force fmode_t)0x80)
> /* File is opened using open(.., 3, ..) and is writeable only for ioctls
> -   (specialy hack for floppy.c) */
> +   (hack for floppy.c) */
> #define FMODE_WRITE_IOCTL      ((__force fmode_t)0x100)
> /* 32bit hashes as llseek() offset (for directories) */
> #define FMODE_32BITHASH         ((__force fmode_t)0x200)
> @@ -819,7 +819,7 @@ void lock_two_nondirectories(struct inode *, struct inode*);
> void unlock_two_nondirectories(struct inode *, struct inode*);
>
> /*
> - * NOTE: in a 32bit arch with a preemptable kernel and
> + * NOTE: in a 32bit arch with a preemptible kernel and
>  * an UP compile the i_size_read/write must be atomic
>  * with respect to the local cpu (unlike with preempt disabled),
>  * but they don't need to be atomic with respect to other cpus like in

Attachment: signature.asc
Description: PGP signature