From: kbuild test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: kbuild-all@01.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, chao@kernel.org,
Chao Yu <yuchao0@huawei.com>
Subject: Re: [PATCH] f2fs: sepearte hot/cold in free nid
Date: Sun, 22 Apr 2018 14:31:09 +0800 [thread overview]
Message-ID: <201804221427.WmgRaqpG%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180420015231.90679-1-yuchao0@huawei.com>
Hi Chao,
I love your patch! Perhaps something to improve:
[auto build test WARNING on f2fs/dev-test]
[also build test WARNING on v4.17-rc1 next-20180420]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Chao-Yu/f2fs-sepearte-hot-cold-in-free-nid/20180421-061929
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
fs/f2fs/node.c:486:15: sparse: expression using sizeof(void)
fs/f2fs/node.c:1744:28: sparse: expression using sizeof(void)
>> fs/f2fs/node.c:2034:6: sparse: symbol 'load_nat_block' was not declared. Should it be static?
fs/f2fs/node.c:2428:27: sparse: expression using sizeof(void)
fs/f2fs/node.c:2523:40: sparse: restricted __le32 degrades to integer
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-04-22 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 1:52 Chao Yu
2018-04-20 2:30 ` [f2fs-dev] " heyunlei
2018-04-20 3:14 ` Chao Yu
2018-04-20 3:37 ` Jaegeuk Kim
2018-04-20 4:04 ` Chao Yu
2018-04-20 9:35 ` Chao Yu
2018-04-23 14:49 ` Jaegeuk Kim
2018-04-23 14:53 ` Chao Yu
2018-04-22 6:31 ` kbuild test robot [this message]
2018-04-22 6:31 ` [RFC PATCH] f2fs: load_nat_block() can be static kbuild test robot
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=201804221427.WmgRaqpG%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@01.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
all inboxes | Powered by JetHome®