From: Randy Dunlap <rdunlap@infradead.org>
To: Chao Yu <yuchao0@huawei.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [PATCH] f2fs: fix defined but not used build warnings
Date: Wed, 11 Jul 2018 20:35:57 -0700 [thread overview]
Message-ID: <14890abc-8ba5-5029-8043-6e27fd4c2b37@infradead.org> (raw)
In-Reply-To: <b6f9275a-854a-d9e3-271b-b2671acd6041@huawei.com>
On 07/09/2018 06:09 PM, Chao Yu wrote:
> On 2018/7/7 11:50, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Fix build warnings in f2fs when CONFIG_PROC_FS is not enabled
>> by marking the unused functions as __maybe_unused.
>>
>> ../fs/f2fs/sysfs.c:519:12: warning: 'segment_info_seq_show' defined but not used [-Wunused-function]
>> ../fs/f2fs/sysfs.c:546:12: warning: 'segment_bits_seq_show' defined but not used [-Wunused-function]
>> ../fs/f2fs/sysfs.c:570:12: warning: 'iostat_info_seq_show' defined but not used [-Wunused-function]
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
>> Cc: Chao Yu <yuchao0@huawei.com>
>> Cc: linux-f2fs-devel@lists.sourceforge.net
>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
Hi,
Who would you like to merge this patch? or could you do so?
thanks,
--
~Randy
next prev parent reply other threads:[~2018-07-12 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 3:50 [PATCH] f2fs: fix defined but not used build warnings Randy Dunlap
2018-07-10 1:09 ` Chao Yu
2018-07-12 3:35 ` Randy Dunlap [this message]
2018-07-12 4:15 ` Jaegeuk Kim
2018-07-12 8:21 ` Chao Yu
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=14890abc-8ba5-5029-8043-6e27fd4c2b37@infradead.org \
--to=rdunlap@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@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).