From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Ian Kent <raven@themaw.net>,
autofs@vger.kernel.org, David Howells <dhowells@redhat.com>,
linux-cachefs@redhat.com, Joel Becker <jlbec@evilplan.org>,
Christoph Hellwig <hch@lst.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>,
"Theodore Y . Ts'o" <tytso@mit.edu>,
linux-fscrypt@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org
Subject: [PATCH 04/10] Documentation: filesystems: directory-locking: drop doubled word
Date: Fri, 3 Jul 2020 14:43:19 -0700 [thread overview]
Message-ID: <20200703214325.31036-5-rdunlap@infradead.org> (raw)
In-Reply-To: <20200703214325.31036-1-rdunlap@infradead.org>
Drop the doubled word "the".
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
---
Documentation/filesystems/directory-locking.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20200701.orig/Documentation/filesystems/directory-locking.rst
+++ linux-next-20200701/Documentation/filesystems/directory-locking.rst
@@ -28,7 +28,7 @@ RENAME_EXCHANGE in flags argument) lock
if the target already exists, lock it. If the source is a non-directory,
lock it. If we need to lock both, lock them in inode pointer order.
Then call the method. All locks are exclusive.
-NB: we might get away with locking the the source (and target in exchange
+NB: we might get away with locking the source (and target in exchange
case) shared.
5) link creation. Locking rules:
@@ -56,7 +56,7 @@ rules:
* call the method.
All ->i_rwsem are taken exclusive. Again, we might get away with locking
-the the source (and target in exchange case) shared.
+the source (and target in exchange case) shared.
The rules above obviously guarantee that all directories that are going to be
read, modified or removed by method will be locked by caller.
next prev parent reply other threads:[~2020-07-03 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 21:43 [PATCH 00/10] Documentation: filesystems: eliminate duplicated words Randy Dunlap
2020-07-03 21:43 ` [PATCH 01/10] Documentation: filesystems: autofs-mount-control: drop doubled words Randy Dunlap
2020-07-06 0:15 ` Ian Kent
2020-07-03 21:43 ` [PATCH 02/10] Documentation: filesystems: caching/operations: drop doubled word Randy Dunlap
2020-07-03 21:43 ` [PATCH 03/10] Documentation: filesystems: configfs: " Randy Dunlap
2020-07-03 21:43 ` Randy Dunlap [this message]
2020-07-03 21:43 ` [PATCH 05/10] Documentation: filesystems: fsverity: " Randy Dunlap
2020-07-07 18:10 ` Eric Biggers
2020-07-03 21:43 ` [PATCH 06/10] Documentation: filesystems: mount_api: " Randy Dunlap
2020-07-03 21:43 ` [PATCH 07/10] Documentation: filesystems: overlayfs: " Randy Dunlap
2020-07-03 21:43 ` [PATCH 08/10] Documentation: filesystems: path-lookup: " Randy Dunlap
2020-07-03 21:43 ` [PATCH 09/10] Documentation: filesystems: sysfs-tagging: " Randy Dunlap
2020-07-03 21:43 ` [PATCH 10/10] Documentation: filesystems: vfs: drop doubled words Randy Dunlap
2020-07-05 20:44 ` [PATCH 00/10] Documentation: filesystems: eliminate duplicated words 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=20200703214325.31036-5-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=autofs@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=raven@themaw.net \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).