[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190313040919.6937-13-tobin@kernel.org>
Date: Wed, 13 Mar 2019 15:09:18 +1100
From: "Tobin C. Harding" <tobin@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: "Tobin C. Harding" <tobin@...nel.org>, linux-doc@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 12/13] docs: filesystems: vfs: Do minor grammar fixes
While converting to RST a few minor grammar mistakes were noticed. Fix
these now the conversion is done.
Fix minor grammar mistakes.
Signed-off-by: Tobin C. Harding <tobin@...nel.org>
---
Documentation/filesystems/vfs.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/filesystems/vfs.rst b/Documentation/filesystems/vfs.rst
index 2cdd4700aba3..c0259538a759 100644
--- a/Documentation/filesystems/vfs.rst
+++ b/Documentation/filesystems/vfs.rst
@@ -1107,13 +1107,13 @@ defined:
- ``d_dname``: called when the pathname of a dentry should be generated.
Useful for some pseudo filesystems (sockfs, pipefs, ...) to delay
pathname generation. (Instead of doing it when dentry is created,
- it's done only when the path is needed.). Real filesystems probably
- dont want to use it, because their dentries are present in global
+ it's done only when the path is needed.) Real filesystems probably
+ don't want to use it, because their dentries are present in global
dcache hash, so their hash should be an invariant. As no lock is
held, d_dname() should not try to modify the dentry itself, unless
appropriate SMP safety is used. CAUTION : d_path() logic is quite
tricky. The correct way to return for example "Hello" is to put it at
- the end of the buffer, and returns a pointer to the first char.
+ the end of the buffer, and return a pointer to the first char.
dynamic_dname() helper function is provided to take care of this.
.. code-block:: c
@@ -1207,7 +1207,7 @@ manipulate dentries:
d_instantiate().
- ``d_instantiate``: add a dentry to the alias hash list for the inode and
- updates the "d_inode" member. The "i_count" member in the inode
+ update the "d_inode" member. The "i_count" member in the inode
structure should be set/incremented. If the inode pointer is NULL, the
dentry is called a "negative dentry". This function is commonly called
when an inode is created for an existing negative dentry.
--
2.21.0
Powered by blists - more mailing lists