| Message ID | 20240908172841.9616-2-dennis.lamerice@gmail.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | docs:filesystems: fix spelling and grammar mistakes in iomap design page | expand |
On Sun, 08 Sep 2024 13:28:42 -0400, Dennis Lam wrote:
>
Applied to the vfs.blocksize branch of the vfs/vfs.git tree.
Patches in the vfs.blocksize 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.blocksize
[1/1] docs:filesystems: fix spelling and grammar mistakes in iomap design page
https://git.kernel.org/vfs/vfs/c/b1daf3f8475f
On Mon, Sep 09, 2024 at 09:53:28AM +0200, Christian Brauner wrote: > On Sun, 08 Sep 2024 13:28:42 -0400, Dennis Lam wrote: > > > > > Applied to the vfs.blocksize branch of the vfs/vfs.git tree. > Patches in the vfs.blocksize branch should appear in linux-next soon. I don't know if it's already too late, but if it isn't: Reviewed-by: Darrick J. Wong <djwong@kernel.org> --D > > 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.blocksize > > [1/1] docs:filesystems: fix spelling and grammar mistakes in iomap design page > https://git.kernel.org/vfs/vfs/c/b1daf3f8475f
diff --git a/Documentation/filesystems/iomap/design.rst b/Documentation/filesystems/iomap/design.rst index f8ee3427bc1a..e2d34085dd0e 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). @@ -426,7 +426,7 @@ iomap is concerned: The exact locking requirements are specific to the filesystem; for certain operations, some of these locks can be elided. -All further mention of locking are *recommendations*, not mandates. +All further mentions of locking are *recommendations*, not mandates. Each filesystem author must figure out the locking for themself. Bugs and Limitations
Signed-off-by: Dennis Lam <dennis.lamerice@gmail.com> --- Documentation/filesystems/iomap/design.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)