From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: update mount option in filesystem/vfat.txt
Date: Sun, 29 Jul 2012 20:32:53 +0900 [thread overview]
Message-ID: <87sjcaiyze.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1343559005-7661-1-git-send-email-linkinjeon@gmail.com> (Namjae Jeon's message of "Sun, 29 Jul 2012 06:50:05 -0400")
Namjae Jeon <linkinjeon@gmail.com> writes:
> update two mount option(discard, nfs) in vfat.txt.
Good catch.
However, "--" doesn't seem to be aligned. Maybe, you are using the TAB
as 4 spaces, or such? Otherwise, looks good to me.
> Signed-off-by: Namjae Jeon <linkinjeon@gmail.com>
> ---
> Documentation/filesystems/vfat.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/filesystems/vfat.txt b/Documentation/filesystems/vfat.txt
> index ead764b..dd322a4 100644
> --- a/Documentation/filesystems/vfat.txt
> +++ b/Documentation/filesystems/vfat.txt
> @@ -137,6 +137,17 @@ errors=panic|continue|remount-ro
> without doing anything or remount the partition in
> read-only mode (default behavior).
>
> +discard -- If set, issues discard/TRIM commands to the block
> + device when blocks are freed. This is useful for SSD devices
> + and sparse/thinly-provisoned LUNs.
> +
> +nfs -- This option maintains an index (cache) of directory
> + inodes by i_logstart which is used by the nfs-related code to
> + improve look-ups.
> +
> + Enable this only if you want to export the FAT filesystem
> + over NFS
> +
> <bool>: 0,1,yes,no,true,false
>
> TODO
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2012-07-29 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 10:50 [PATCH] Documentation: update mount option in filesystem/vfat.txt Namjae Jeon
2012-07-29 11:32 ` OGAWA Hirofumi [this message]
2012-07-29 12:14 ` Namjae Jeon
2012-07-30 12:00 ` Steven J. Magnani
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=87sjcaiyze.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=linkinjeon@gmail.com \
--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