On 08/18/13 21:50, Masanari Iida wrote:
> Correct spelling typo in Documentations/filesystems.
> 
> Signed-off-by: Masanari Iida <[email protected]>

This probably can also go via [email protected].

Acked-by: Randy Dunlap <[email protected]>

Thanks.

> 
> ---
>  Documentation/filesystems/btrfs.txt     | 2 +-
>  Documentation/filesystems/f2fs.txt      | 2 +-
>  Documentation/filesystems/nfs/Exporting | 2 +-
>  Documentation/filesystems/qnx6.txt      | 2 +-
>  Documentation/filesystems/xfs.txt       | 2 +-
>  5 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/filesystems/btrfs.txt 
> b/Documentation/filesystems/btrfs.txt
> index b349d57..9dae594 100644
> --- a/Documentation/filesystems/btrfs.txt
> +++ b/Documentation/filesystems/btrfs.txt
> @@ -87,7 +87,7 @@ Unless otherwise specified, all options default to off.
>  
>    device=<devicepath>
>       Specify a device during mount so that ioctls on the control device
> -     can be avoided.  Especialy useful when trying to mount a multi-device
> +     can be avoided.  Especially useful when trying to mount a multi-device
>       setup as root.  May be specified multiple times for multiple devices.
>  
>    discard
> diff --git a/Documentation/filesystems/f2fs.txt 
> b/Documentation/filesystems/f2fs.txt
> index 3cd27be..3b57456 100644
> --- a/Documentation/filesystems/f2fs.txt
> +++ b/Documentation/filesystems/f2fs.txt
> @@ -216,7 +216,7 @@ The dump.f2fs shows the information of specific inode and 
> dumps SSA and SIT to
>  file. Each file is dump_ssa and dump_sit.
>  
>  The dump.f2fs is used to debug on-disk data structures of the f2fs 
> filesystem.
> -It shows on-disk inode information reconized by a given inode number, and is
> +It shows on-disk inode information recognized by a given inode number, and is
>  able to dump all the SSA and SIT entries into predefined files, ./dump_ssa 
> and
>  ./dump_sit respectively.
>  
> diff --git a/Documentation/filesystems/nfs/Exporting 
> b/Documentation/filesystems/nfs/Exporting
> index 09994c2..e543b1a 100644
> --- a/Documentation/filesystems/nfs/Exporting
> +++ b/Documentation/filesystems/nfs/Exporting
> @@ -93,7 +93,7 @@ For a filesystem to be exportable it must:
>     2/ make sure that d_splice_alias is used rather than d_add
>        when ->lookup finds an inode for a given parent and name.
>  
> -      If inode is NULL, d_splice_alias(inode, dentry) is eqivalent to
> +      If inode is NULL, d_splice_alias(inode, dentry) is equivalent to
>  
>               d_add(dentry, inode), NULL
>  
> diff --git a/Documentation/filesystems/qnx6.txt 
> b/Documentation/filesystems/qnx6.txt
> index 99e9018..4086797 100644
> --- a/Documentation/filesystems/qnx6.txt
> +++ b/Documentation/filesystems/qnx6.txt
> @@ -149,7 +149,7 @@ Bitmap system area
>  ------------------
>  
>  The bitmap itself is divided into three parts.
> -First the system area, that is split into two halfs.
> +First the system area, that is split into two halves.
>  Then userspace.
>  
>  The requirement for a static, fixed preallocated system area comes from how
> diff --git a/Documentation/filesystems/xfs.txt 
> b/Documentation/filesystems/xfs.txt
> index 12525b1..5be51fd 100644
> --- a/Documentation/filesystems/xfs.txt
> +++ b/Documentation/filesystems/xfs.txt
> @@ -135,7 +135,7 @@ default behaviour.
>       If the memory cost of 8 log buffers is too high on small
>       systems, then it may be reduced at some cost to performance
>       on metadata intensive workloads. The logbsize option below
> -     controls the size of each buffer and so is also relevent to
> +     controls the size of each buffer and so is also relevant to
>       this case.
>  
>    logbsize=value
> 


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to