diff options
| author | Bjorn Helgaas <bhelgaas@google.com> | 2023-08-14 16:28:22 -0500 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2023-08-18 11:29:03 -0600 |
| commit | d56b699d76d1b352f7a3d3a0a3e91c79b8612d94 (patch) | |
| tree | 2a368f3e2e17f7a516bf39e055f79d8c79a74885 /Documentation/filesystems/porting.rst | |
| parent | ebab9426cd73c45945b44344ca904b343f0ca070 (diff) | |
| download | linux-stable-d56b699d76d1b352f7a3d3a0a3e91c79b8612d94.tar.gz linux-stable-d56b699d76d1b352f7a3d3a0a3e91c79b8612d94.tar.bz2 linux-stable-d56b699d76d1b352f7a3d3a0a3e91c79b8612d94.zip | |
Documentation: Fix typos
Fix typos in Documentation.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Link: https://lore.kernel.org/r/20230814212822.193684-4-helgaas@kernel.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/filesystems/porting.rst')
| -rw-r--r-- | Documentation/filesystems/porting.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/filesystems/porting.rst b/Documentation/filesystems/porting.rst index d2d684ae7798..ffafd93001df 100644 --- a/Documentation/filesystems/porting.rst +++ b/Documentation/filesystems/porting.rst @@ -177,7 +177,7 @@ settles down a bit. **mandatory** s_export_op is now required for exporting a filesystem. -isofs, ext2, ext3, resierfs, fat +isofs, ext2, ext3, reiserfs, fat can be used as examples of very different filesystems. --- @@ -470,7 +470,7 @@ has been taken to VFS and filesystems need to provide a non-NULL **mandatory** If you implement your own ->llseek() you must handle SEEK_HOLE and -SEEK_DATA. You can hanle this by returning -EINVAL, but it would be nicer to +SEEK_DATA. You can handle this by returning -EINVAL, but it would be nicer to support it in some way. The generic handler assumes that the entire file is data and there is a virtual hole at the end of the file. So if the provided offset is less than i_size and SEEK_DATA is specified, return the same offset. @@ -517,7 +517,7 @@ The witch is dead! Well, 2/3 of it, anyway. ->d_revalidate() and ->create() doesn't take ``struct nameidata *``; unlike the previous two, it gets "is it an O_EXCL or equivalent?" boolean argument. Note that -local filesystems can ignore tha argument - they are guaranteed that the +local filesystems can ignore this argument - they are guaranteed that the object doesn't exist. It's remote/distributed ones that might care... --- |