From: Glenn Washburn <development@efficientek.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Glenn Washburn <development@efficientek.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Tobin C. Harding" <tobin@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] docs: Correct missing "d_" prefix for dentry_operations member d_weak_revalidate
Date: Mon, 27 Feb 2023 12:40:42 -0600 [thread overview]
Message-ID: <20230227184042.2375235-1-development@efficientek.com> (raw)
The details for struct dentry_operations member d_weak_revalidate is
missing a "d_" prefix.
Fixes: af96c1e304f7 (docs: filesystems: vfs: Convert vfs.txt to RST)
Signed-off-by: Glenn Washburn <development@efficientek.com>
---
Documentation/filesystems/vfs.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/vfs.rst b/Documentation/filesystems/vfs.rst
index c53f30251a66..f3b344f0c0a4 100644
--- a/Documentation/filesystems/vfs.rst
+++ b/Documentation/filesystems/vfs.rst
@@ -1222,7 +1222,7 @@ defined:
return
-ECHILD and it will be called again in ref-walk mode.
-``_weak_revalidate``
+``d_weak_revalidate``
called when the VFS needs to revalidate a "jumped" dentry. This
is called when a path-walk ends at dentry that was not acquired
by doing a lookup in the parent directory. This includes "/",
base-commit: 7fa08de735e41001a70c8ca869b2b159d74c2339
--
2.30.2
next reply other threads:[~2023-02-27 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 18:40 Glenn Washburn [this message]
2023-02-27 18:59 ` [PATCH] docs: Correct missing "d_" prefix for dentry_operations member d_weak_revalidate Matthew Wilcox
2023-03-07 17:24 ` 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=20230227184042.2375235-1-development@efficientek.com \
--to=development@efficientek.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tobin@kernel.org \
--cc=willy@infradead.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).