From: I Hsin Cheng <richard120310@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: corbet@lwn.net, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] docs: vfs: Update struct file_system_type
Date: Thu, 27 Mar 2025 22:29:03 +0800 [thread overview]
Message-ID: <Z-Vgrx0XSDASGnpg@vaxr-BM6660-BM6360> (raw)
In-Reply-To: <Z-AZiYwkE9PsST90@casper.infradead.org>
On Sun, Mar 23, 2025 at 02:24:09PM +0000, Matthew Wilcox wrote:
> On Sun, Mar 23, 2025 at 11:47:25AM +0800, I Hsin Cheng wrote:
> > The structure definition now in the kernel adds macros defining the
> > value of "fs_flags", and the value "FS_NO_DCACHE" no longer exists,
> > update it to an existing flag value.
>
> What value does it add to duplicate these flag definitions in the
> documentation? I would not do this.
>
> > @@ -140,7 +148,7 @@ members are defined:
> > "msdos" and so on
> >
> > ``fs_flags``
> > - various flags (i.e. FS_REQUIRES_DEV, FS_NO_DCACHE, etc.)
> > + various flags (i.e. FS_REQUIRES_DEV, FS_BINARY_MOUNTDATA, etc.)
>
> This should be "eg.", not "i.e."
Hi Matthew,
Thanks for your kindly reply!
> What value does it add to duplicate these flag definitions in the
> documentation? I would not do this.
I thought the documentation should follow the exact code as in the
kernel, if it only serves as a roughly example, I agree with you then.
> This should be "eg.", not "i.e."
Sure, I'll change it and send v2.
Let me know if anything more is needed to be correct, thanks!
Best regards,
I Hsin Cheng
prev parent reply other threads:[~2025-03-27 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 3:47 [PATCH] docs: vfs: Update struct file_system_type I Hsin Cheng
2025-03-23 14:24 ` Matthew Wilcox
2025-03-27 14:29 ` I Hsin Cheng [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=Z-Vgrx0XSDASGnpg@vaxr-BM6660-BM6360 \
--to=richard120310@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=willy@infradead.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).