linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <tobin@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
	linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 12/13] docs: filesystems: vfs: Do minor grammar fixes
Date: Wed, 13 Mar 2019 15:09:18 +1100	[thread overview]
Message-ID: <20190313040919.6937-13-tobin@kernel.org> (raw)
In-Reply-To: <20190313040919.6937-1-tobin@kernel.org>

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@kernel.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


  parent reply	other threads:[~2019-03-13  4:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13  4:09 [PATCH 00/13] Convert vfs.txt to vfs.rst Tobin C. Harding
2019-03-13  4:09 ` [PATCH 01/13] docs: filesystems: vfs: Remove space before tab Tobin C. Harding
2019-03-13  4:09 ` [PATCH 02/13] docs: filesystems: vfs: Use uniform space after period Tobin C. Harding
2019-03-13  4:09 ` [PATCH 03/13] docs: filesystems: vfs: Use 72 character column width Tobin C. Harding
2019-03-13  4:09 ` [PATCH 04/13] docs: filesystems: vfs: Use uniform spacing around headings Tobin C. Harding
2019-03-13  4:09 ` [PATCH 05/13] docs: filesystems: vfs: Use correct initial heading Tobin C. Harding
2019-03-13  4:09 ` [PATCH 06/13] docs: filesystems: vfs: Use SPDX identifier Tobin C. Harding
2019-03-13  4:09 ` [PATCH 07/13] docs: filesystems: vfs: Fix pre-amble indentation Tobin C. Harding
2019-03-13  4:09 ` [PATCH 08/13] docs: filesystems: vfs: Use list character for lists Tobin C. Harding
2019-03-13  4:09 ` [PATCH 09/13] docs: filesystems: vfs: Add code-block and txt->RST Tobin C. Harding
2019-03-13  4:09 ` [PATCH 10/13] docs: filesystems: vfs: Use ticks for listed items Tobin C. Harding
2019-03-13  4:09 ` [PATCH 11/13] docs: filesystems: vfs: Clean up lists Tobin C. Harding
2019-03-13  4:09 ` Tobin C. Harding [this message]
2019-03-13  4:09 ` [PATCH 13/13] docs: filesystems: vfs: Use backticks to guard star Tobin C. Harding
2019-03-18  1:46 ` [PATCH 00/13] Convert vfs.txt to vfs.rst Randy Dunlap
2019-03-18  3:34   ` Tobin C. Harding
2019-03-18 17:42     ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190313040919.6937-13-tobin@kernel.org \
    --to=tobin@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).