From: Arnd Bergmann <arnd@arndb.de>
To: Chao Yu <yuchao0@huawei.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
Fan Li <fanofcode.li@samsung.com>,
Weichao Guo <guoweichao@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] f2fs: replace a build-time warning with runtime WARN_ON
Date: Wed, 2 Nov 2016 14:53:11 +0100 [thread overview]
Message-ID: <201611021453.11393.arnd@arndb.de> (raw)
In-Reply-To: <c0d9b688-0ac9-6b45-62cc-02e71f2aa331@huawei.com>
On Wednesday 02 November 2016, Chao Yu wrote:
> Hi Arnd, Jaegeuk,
>
> It is trivial, but it's better keep commit *title*, commit log and code
> consistent. :)
Sorry for my silly mistake, sent it again with a new subject now.
Arnd
prev parent reply other threads:[~2016-11-02 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 15:32 [PATCH v2] f2fs: replace a build-time warning with runtime WARN_ON Arnd Bergmann
2016-11-02 7:09 ` Chao Yu
2016-11-02 13:53 ` Arnd Bergmann [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=201611021453.11393.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=fanofcode.li@samsung.com \
--cc=guoweichao@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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 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).