From: Viacheslav Shevchuk <slavik.a.shevchuk@gmail.com>
To: miklos@szeredi.hu
Cc: corbet@lwn.net, rdunlap@infradead.org, skhan@linuxfoundation.org,
fuse-devel@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Viacheslav Shevchuk <slavik.a.shevchuk@gmail.com>
Subject: [PATCH] docs: fuse: fix typos in fuse-caches.rst
Date: Tue, 3 Nov 2026 11:44:07 +0200 [thread overview]
Message-ID: <20261103094407.912-1-slavik.a.shevchuk@gmail.com> (raw)
Fix two misspellings of "successfully" and change "then next time"
to "the next time".
The misspellings were found with the help of an AI coding assistant
(Claude Opus 5.5) by grepping Documentation/ for the entries in
scripts/spelling.txt.
Signed-off-by: Viacheslav Shevchuk <slavik.a.shevchuk@gmail.com>
---
Documentation/filesystems/fuse/fuse-caches.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/fuse/fuse-caches.rst b/Documentation/filesystems/fuse/fuse-caches.rst
index 0778dd3d..d19592c6 100644
--- a/Documentation/filesystems/fuse/fuse-caches.rst
+++ b/Documentation/filesystems/fuse/fuse-caches.rst
@@ -156,11 +156,11 @@ 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
+that a ``FUSE_LOOKUP`` will be sent to user-space the next time it needs to be
looked up. It can be set to 0 in several occasions:
- When the user-space FUSE server explicitly requests a dentry to be invalidated
--
2.56.0.windows.1
next reply other threads:[~2026-11-03 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 9:44 Viacheslav Shevchuk [this message]
2026-11-03 17:07 ` Randy Dunlap
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=20261103094407.912-1-slavik.a.shevchuk@gmail.com \
--to=slavik.a.shevchuk@gmail.com \
--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®