From: Jonathan Corbet <corbet@lwn.net>
To: Masanari Iida <standby24x7@gmail.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH][trivial] Doc: treewide : Fix typos in DocBook/filesystem.xml
Date: Tue, 2 Feb 2016 12:27:20 -0700 [thread overview]
Message-ID: <20160202122720.76bb700d@lwn.net> (raw)
In-Reply-To: <1454419866-6010-1-git-send-email-standby24x7@gmail.com>
On Tue, 2 Feb 2016 22:31:06 +0900
Masanari Iida <standby24x7@gmail.com> 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.
As Randy said, "tradeoff" is fine. This should probably go to Al Viro,
though, for merging via his VFS tree.
Thanks,
jon
prev parent reply other threads:[~2016-02-02 19:27 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
2016-02-02 19:27 ` Jonathan Corbet [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=20160202122720.76bb700d@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--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