From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: shaikh kamaluddin <shaikhkamal2012@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: filesystems: vfat: fix 'whic' spelling
Date: Sun, 26 Jul 2026 18:41:52 +0900 [thread overview]
Message-ID: <87v7a284v3.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <amXU4Kkcj7tjh8Jl@acer-nitro-anv15-41>
shaikh kamaluddin <shaikhkamal2012@gmail.com> writes:
>> > diff --git a/Documentation/filesystems/vfat.rst b/Documentation/filesystems/vfat.rst
>> > index b289c4449cd0..f408699ce50f 100644
>> > --- a/Documentation/filesystems/vfat.rst
>> > +++ b/Documentation/filesystems/vfat.rst
>> > @@ -361,7 +361,7 @@ the following:
>> >
>> > <proceeding files...>
>> > <slot #3, id = 0x43, characters = "h is long">
>> > - <slot #2, id = 0x02, characters = "xtension whic">
>> > + <slot #2, id = 0x02, characters = "xtension which">
>> > <slot #1, id = 0x01, characters = "My Big File.E">
>> > <directory entry, name = "MYBIGFIL.EXT">
>>
>> --
>> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
>
> Hi,
>
> Please drop this patch — I got it wrong. The "whic" here is
> intentional: each LFN slot holds 13 characters, and the word
> "which" is deliberately split across slot #2 ("xtension whic")
> and slot #3 ("h is long"). The concatenated name is
> "My Big File.Extension which is long".
>
> My change makes slot #2 fourteen characters and would render the
> example incorrect. Sorry for the noise, and thanks for the ack —
> but it shouldn't be applied.
Thanks for telling.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2026-07-26 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 6:49 shaikh.kamal
2026-07-26 8:31 ` OGAWA Hirofumi
2026-07-26 9:35 ` shaikh kamaluddin
2026-07-26 9:41 ` OGAWA Hirofumi [this message]
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=87v7a284v3.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaikhkamal2012@gmail.com \
--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®