From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Christian Brauner <brauner@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
linux-fsdevel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [PATCH] libfs: fix table format warning
Date: Mon, 3 Jul 2023 21:46:43 -0700 [thread overview]
Message-ID: <20230704044643.8622-1-rdunlap@infradead.org> (raw)
Drop the unnecessary colon to make the table formatting correct.
The colons are not needed and this file uses them sometimes and
doesn't at other times. Generally they are not preferred in
documentation tables IMO.
Also extend the table line widths to match the table text.
Fixes: 7a3472ae9614 ("libfs: Add directory operations for stable offsets")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Link: https://lore.kernel.org/linux-next/20230704135149.014516c7@canb.auug.org.au/T/#u
Cc: Christian Brauner <brauner@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-fsdevel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
---
Documentation/filesystems/locking.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff -- a/Documentation/filesystems/locking.rst b/Documentation/filesystems/locking.rst
--- a/Documentation/filesystems/locking.rst
+++ b/Documentation/filesystems/locking.rst
@@ -90,9 +90,9 @@ prototypes::
locking rules:
all may block
-============== =============================================
+============== ==================================================
ops i_rwsem(inode)
-============== =============================================
+============== ==================================================
lookup: shared
create: exclusive
link: exclusive (both)
@@ -116,8 +116,8 @@ atomic_open: shared (exclusive if O_CREA
tmpfile: no
fileattr_get: no or exclusive
fileattr_set: exclusive
-get_offset_ctx: no
-============== =============================================
+get_offset_ctx no
+============== ==================================================
Additionally, ->rmdir(), ->unlink() and ->rename() have ->i_rwsem
next reply other threads:[~2023-07-04 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 4:46 Randy Dunlap [this message]
2023-07-04 7:47 ` [PATCH] libfs: fix table format warning Christian Brauner
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=20230704044643.8622-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).