From: kth <kangtaeho2456@gmail.com>
To: corbet@lwn.net
Cc: kangtaeho2456@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] fs: Fix typo from smpfs to smbfs in filesystem documentation
Date: Tue, 11 Mar 2025 02:34:20 +0800 [thread overview]
Message-ID: <20250310183420.324958-1-kangtaeho2456@gmail.com> (raw)
The documentation incorrectly reffered to 'smbfs' as 'smpfs'. This change corrects that typo to ensure the documentation is accurate and not misleading.
Signed-off-by: Kang Taeho <kangtaeho2456@gmail.com>
---
Documentation/admin-guide/highuid.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/highuid.rst b/Documentation/admin-guide/highuid.rst
index 6ee70465c0ea..9239067563a1 100644
--- a/Documentation/admin-guide/highuid.rst
+++ b/Documentation/admin-guide/highuid.rst
@@ -64,7 +64,7 @@ What's left to be done for 32-bit UIDs on all Linux architectures:
Other filesystems have not been checked yet.
-- The ncpfs and smpfs filesystems cannot presently use 32-bit UIDs in
+- The ncpfs and smbfs filesystems cannot presently use 32-bit UIDs in
all ioctl()s. Some new ioctl()s have been added with 32-bit UIDs, but
more are needed. (as well as new user<->kernel data structures)
--
2.48.1
next reply other threads:[~2025-03-10 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 18:34 kth [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-10 18:41 [PATCH] fs: Fix typo from smpfs to smbfs in filesystem documentation kth
2025-03-10 19:28 ` Matthew Wilcox
2025-03-12 22:30 ` 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=20250310183420.324958-1-kangtaeho2456@gmail.com \
--to=kangtaeho2456@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).