From: Chao Yu <chao@kernel.org>
To: Wei Yongjun <weiyj.lk@gmail.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Changman Lee <cm224.lee@samsung.com>,
Chao Yu <yuchao0@huawei.com>
Cc: Wei Yongjun <weiyongjun1@huawei.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH -next] f2fs: fix non static symbol warning
Date: Thu, 25 Aug 2016 22:11:21 +0800 [thread overview]
Message-ID: <a5ea9c94-8f7f-0980-7a44-942f79785fcd@kernel.org> (raw)
In-Reply-To: <1471965839-8389-1-git-send-email-weiyj.lk@gmail.com>
On 2016/8/23 23:23, Wei Yongjun wrote:
> From: Wei Yongjun <weiyongjun1@huawei.com>
>
> Fixes the following sparse warning:
>
> fs/f2fs/data.c:969:12: warning:
> symbol 'f2fs_grab_bio' was not declared. Should it be static?
>
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
Acked-by: Chao Yu <yuchao0@huawei.com>
------------------------------------------------------------------------------
prev parent reply other threads:[~2016-08-25 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 15:23 [PATCH -next] f2fs: fix non static symbol warning Wei Yongjun
2016-08-25 14:11 ` Chao Yu [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=a5ea9c94-8f7f-0980-7a44-942f79785fcd@kernel.org \
--to=chao@kernel.org \
--cc=cm224.lee@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=weiyj.lk@gmail.com \
--cc=weiyongjun1@huawei.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 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).