From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>,
jaegeuk@kernel.org
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, chao@kernel.org,
Chao Yu <yuchao0@huawei.com>
Subject: Re: [PATCH v2] f2fs: move ioctl interface definitions to separated file
Date: Sat, 31 Oct 2020 02:09:04 +0800 [thread overview]
Message-ID: <202010310250.u4WtpViN-lkp@intel.com> (raw)
In-Reply-To: <20201030072610.57155-1-yuchao0@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 3515 bytes --]
Hi Chao,
I love your patch! Yet something to improve:
[auto build test ERROR on f2fs/dev-test]
[also build test ERROR on linus/master v5.10-rc1 next-20201030]
[cannot apply to linux/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Chao-Yu/f2fs-move-ioctl-interface-definitions-to-separated-file/20201030-152809
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
config: x86_64-randconfig-a013-20201030 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project fa5a13276764a2657b3571fa3c57b07ee5d2d661)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://github.com/0day-ci/linux/commit/652525531fd95cc9ef1011882abec714d0d853dc
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Chao-Yu/f2fs-move-ioctl-interface-definitions-to-separated-file/20201030-152809
git checkout 652525531fd95cc9ef1011882abec714d0d853dc
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <built-in>:1:
>> ./usr/include/linux/f2fs.h:58:2: error: unknown type name 'u32'
u32 sync;
^
>> ./usr/include/linux/f2fs.h:59:2: error: unknown type name 'u64'
u64 start;
^
./usr/include/linux/f2fs.h:60:2: error: unknown type name 'u64'
u64 len;
^
./usr/include/linux/f2fs.h:64:2: error: unknown type name 'u64'
u64 start;
^
./usr/include/linux/f2fs.h:65:2: error: unknown type name 'u64'
u64 len;
^
./usr/include/linux/f2fs.h:69:2: error: unknown type name 'u32'
u32 dst_fd; /* destination fd */
^
./usr/include/linux/f2fs.h:70:2: error: unknown type name 'u64'
u64 pos_in; /* start position in src_fd */
^
./usr/include/linux/f2fs.h:71:2: error: unknown type name 'u64'
u64 pos_out; /* start position in dst_fd */
^
./usr/include/linux/f2fs.h:72:2: error: unknown type name 'u64'
u64 len; /* size to move */
^
./usr/include/linux/f2fs.h:76:2: error: unknown type name 'u32'
u32 dev_num; /* device number to flush */
^
./usr/include/linux/f2fs.h:77:2: error: unknown type name 'u32'
u32 segments; /* # of segments to flush */
^
./usr/include/linux/f2fs.h:81:2: error: unknown type name 'u64'
u64 start;
^
./usr/include/linux/f2fs.h:82:2: error: unknown type name 'u64'
u64 len;
^
./usr/include/linux/f2fs.h:83:2: error: unknown type name 'u64'
u64 flags;
^
14 errors generated.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 36290 bytes --]
prev parent reply other threads:[~2020-10-30 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 7:26 [PATCH v2] f2fs: move ioctl interface definitions to separated file Chao Yu
2020-10-30 12:30 ` Jaegeuk Kim
2020-10-30 15:03 ` Chao Yu
2020-10-30 16:55 ` [f2fs-dev] " Eric Biggers
2020-10-31 0:32 ` Chao Yu
2020-10-30 18:09 ` kernel test robot [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=202010310250.u4WtpViN-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@lists.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