linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: kth <kangtaeho2456@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: Fix typo from smpfs to smbfs in filesystem documentation
Date: Mon, 10 Mar 2025 19:28:05 +0000	[thread overview]
Message-ID: <Z889RfnudqMc5r_e@casper.infradead.org> (raw)
In-Reply-To: <20250310184129.328482-1-kangtaeho2456@gmail.com>

On Tue, Mar 11, 2025 at 02:41:29AM +0800, kth wrote:
> The documentation incorrectly referred 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

ncpfs doesn't exist any more; it was removed many years ago.  And the
smbfs that is referred to here was replaced by cifs many years ago.

I have a feeling the entire highuid document should be deleted.  It
describes a transition that happened 25 years ago.

  reply	other threads:[~2025-03-10 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 18:41 [PATCH] fs: Fix typo from smpfs to smbfs in filesystem documentation kth
2025-03-10 19:28 ` Matthew Wilcox [this message]
2025-03-12 22:30   ` Jonathan Corbet
  -- strict thread matches above, loose matches on Subject: below --
2025-03-10 18:34 kth

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=Z889RfnudqMc5r_e@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=corbet@lwn.net \
    --cc=kangtaeho2456@gmail.com \
    --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).