linux-kernel - Re: [PATCH] Fix spelling and gramatical errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240807142511.GA6051@frogsfrogsfrogs>
Date: Wed, 7 Aug 2024 07:25:11 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: Xiaxi Shen <shenxiaxi26@...il.com>
Cc: brauner@...nel.org, corbet@....net, skhan@...uxfoundation.org,
	javier.carrasco.cruz@...il.com, linux-xfs@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix spelling and gramatical errors

On Wed, Aug 07, 2024 at 12:05:36AM -0700, Xiaxi Shen wrote:
> Fixed 3 typos in design.rst
> 
> Signed-off-by: Xiaxi Shen <shenxiaxi26@...il.com>

Thanks for the fixes,
Reviewed-by: Darrick J. Wong <djwong@...nel.org>

--D

> ---
>  Documentation/filesystems/iomap/design.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/filesystems/iomap/design.rst b/Documentation/filesystems/iomap/design.rst
> index f8ee3427bc1a..37594e1c5914 100644
> --- a/Documentation/filesystems/iomap/design.rst
> +++ b/Documentation/filesystems/iomap/design.rst
> @@ -142,9 +142,9 @@ Definitions
>   * **pure overwrite**: A write operation that does not require any
>     metadata or zeroing operations to perform during either submission
>     or completion.
> -   This implies that the fileystem must have already allocated space
> +   This implies that the filesystem must have already allocated space
>     on disk as ``IOMAP_MAPPED`` and the filesystem must not place any
> -   constaints on IO alignment or size.
> +   constraints on IO alignment or size.
>     The only constraints on I/O alignment are device level (minimum I/O
>     size and alignment, typically sector size).
>  
> @@ -394,7 +394,7 @@ iomap is concerned:
>  
>   * The **upper** level primitive is provided by the filesystem to
>     coordinate access to different iomap operations.
> -   The exact primitive is specifc to the filesystem and operation,
> +   The exact primitive is specific to the filesystem and operation,
>     but is often a VFS inode, pagecache invalidation, or folio lock.
>     For example, a filesystem might take ``i_rwsem`` before calling
>     ``iomap_file_buffered_write`` and ``iomap_file_unshare`` to prevent
> -- 
> 2.34.1
> 
>