| Message ID | 20240807070536.14536-1-shenxiaxi26@gmail.com (mailing list archive) |
|---|---|
| State | Accepted, archived |
| Headers | show |
| Series | Fix spelling and gramatical errors | expand |
On Wed, Aug 07, 2024 at 12:05:36AM GMT, Xiaxi Shen wrote: > Fixed 3 typos in design.rst > > Signed-off-by: Xiaxi Shen <shenxiaxi26@gmail.com> > --- > Documentation/filesystems/iomap/design.rst | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com> > > 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 > >
On Wed, 07 Aug 2024 00:05:36 -0700, Xiaxi Shen wrote: > Fixed 3 typos in design.rst > > Applied to the vfs.misc branch of the vfs/vfs.git tree. Patches in the vfs.misc branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs.misc [1/1] Fix spelling and gramatical errors https://git.kernel.org/vfs/vfs/c/9ba1824cc875
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@gmail.com> Thanks for the fixes, Reviewed-by: Darrick J. Wong <djwong@kernel.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 > >
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
Fixed 3 typos in design.rst Signed-off-by: Xiaxi Shen <shenxiaxi26@gmail.com> --- Documentation/filesystems/iomap/design.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)