From: Wei Lixiang <weilixiang@kylinos.cn>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
fuse-devel@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: fuse: fix spelling of 'successfully'
Date: Mon, 2 Nov 2026 17:38:27 +0800 [thread overview]
Message-ID: <20261102093827.6-1-weilixiang@kylinos.cn> (raw)
Fix two misspellings of 'successfully' in the FUSE dentry cache
documentation. No functional change.
Signed-off-by: Wei Lixiang <weilixiang@kylinos.cn>
---
Documentation/filesystems/fuse/fuse-caches.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/fuse/fuse-caches.rst b/Documentation/filesystems/fuse/fuse-caches.rst
index 0778dd3d357f..de1a452fdd31 100644
--- a/Documentation/filesystems/fuse/fuse-caches.rst
+++ b/Documentation/filesystems/fuse/fuse-caches.rst
@@ -156,8 +156,8 @@ in several occasions:
- When a new file system object is created (e.g. ``FUSE_CREATE``,
``FUSE_MKDIR``, etc).
-- When a lookup is sucessfully performed.
-- When a dentry is sucessfully revalidated (``->d_revalidate()``).
+- When a lookup is successfully performed.
+- When a dentry is successfully revalidated (``->d_revalidate()``).
A dentry expiry time can be set to 0, indicating that it is stale. This means
that a ``FUSE_LOOKUP`` will be sent to user-space then next time it needs to be
--
2.25.1
next reply other threads:[~2026-11-02 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 9:38 Wei Lixiang [this message]
2026-11-02 17:02 ` Randy Dunlap
2026-11-12 15:01 ` 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=20261102093827.6-1-weilixiang@kylinos.cn \
--to=weilixiang@kylinos.cn \
--cc=corbet@lwn.net \
--cc=fuse-devel@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®