From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org, trivial@kernel.org,
akpm@linux-foundation.org, corbet@lwn.net
Subject: Re: [PATCH][trivial] Doc: treewide : Fix typos in DocBook/filesystem.xml
Date: Tue, 2 Feb 2016 08:46:59 -0800 [thread overview]
Message-ID: <56B0DD83.7030208@infradead.org> (raw)
In-Reply-To: <1454419866-6010-1-git-send-email-standby24x7@gmail.com>
On 02/02/16 05:31, Masanari Iida wrote:
> This patch fix spelling typos found in DocBook/filesystem.xml.
> It is because the file was generated from comments in code,
> I have to fix the comments in codes, instead of xml file.
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> fs/inode.c | 2 +-
> fs/jbd2/recovery.c | 2 +-
> fs/jbd2/transaction.c | 6 +++---
> fs/super.c | 2 +-
> 4 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/fs/inode.c b/fs/inode.c
> index 9f62db3..584b81a 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -1308,7 +1308,7 @@ EXPORT_SYMBOL(ilookup);
> * function must never block --- find_inode() can block in
> * __wait_on_freeing_inode() --- or when the caller can not increment
> * the reference count because the resulting iput() might cause an
> - * inode eviction. The tradeoff is that the @match funtion must be
> + * inode eviction. The trade off is that the @match function must be
"tradeoff" is a good word.
All of the others are good changes.
Thanks.
> * very carefully implemented.
> */
> struct inode *find_inode_nowait(struct super_block *sb,
--
~Randy
next prev parent reply other threads:[~2016-02-02 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 13:31 [PATCH][trivial] Doc: treewide : Fix typos in DocBook/filesystem.xml Masanari Iida
2016-02-02 16:46 ` Randy Dunlap [this message]
2016-02-02 19:27 ` Jonathan Corbet
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=56B0DD83.7030208@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@gmail.com \
--cc=trivial@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