From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Masanari Iida <standby24x7@gmail.com>
Cc: linux-kernel@vger.kernel.org, yuchao0@huawei.com,
linux-f2fs-devel@lists.sourceforge.net, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [linux-next] [PATCH] Doc: f2fs: Fix typo in Documentation/filesystems/f2fs.txt
Date: Tue, 24 Jan 2017 13:36:42 +0900 [thread overview]
Message-ID: <20170124043642.GD1566@jaegeuk.local> (raw)
In-Reply-To: <20170124034755.20965-1-standby24x7@gmail.com>
Hello,
Applied to f2fs.git.
Thanks,
On 01/24, Masanari Iida wrote:
> This patch fix a typo in f2fs.txt
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> Documentation/filesystems/f2fs.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/f2fs.txt b/Documentation/filesystems/f2fs.txt
> index d99faced79cb..0ab33d4c8406 100644
> --- a/Documentation/filesystems/f2fs.txt
> +++ b/Documentation/filesystems/f2fs.txt
> @@ -131,7 +131,7 @@ inline_dentry Enable the inline dir feature: data in new created
> directory entries can be written into inode block. The
> space of inode block which is used to store inline
> dentries is limited to ~3.4k.
> -noinline_dentry Diable the inline dentry feature.
> +noinline_dentry Disable the inline dentry feature.
> flush_merge Merge concurrent cache_flush commands as much as possible
> to eliminate redundant command issues. If the underlying
> device handles the cache_flush command relatively slowly,
> --
> 2.11.0.453.g787f75f0567a
prev parent reply other threads:[~2017-01-24 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 3:47 [linux-next] [PATCH] Doc: f2fs: Fix typo in Documentation/filesystems/f2fs.txt Masanari Iida
2017-01-24 4:36 ` Jaegeuk Kim [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=20170124043642.GD1566@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@gmail.com \
--cc=yuchao0@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.