From: kbuild test robot <lkp@intel.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH v4 1/2] btrfs: Move on-disk structure definition to btrfs_tree.h
Date: Thu, 23 Apr 2020 19:32:56 +0800 [thread overview]
Message-ID: <202004231935.sAvDUszh%lkp@intel.com> (raw)
In-Reply-To: <20200415084113.64378-2-wqu@suse.com>
[-- Attachment #1: Type: text/plain, Size: 3166 bytes --]
Hi Qu,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v5.7-rc1]
[also build test ERROR on next-20200423]
[cannot apply to btrfs/next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Qu-Wenruo/btrfs-Reformat-and-make-btrfs_tree-h-self-contained/20200416-023848
base: 8f3d9f354286745c751374f5f1fcafee6b3f3136
config: x86_64-randconfig-s1-20200423 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from ./usr/include/linux/btrfs.h:24:0,
from <command-line>:32:
>> ./usr/include/linux/btrfs_tree.h:1110:2: error: unknown type name 'u8'
u8 tree_root_level;
^~
./usr/include/linux/btrfs_tree.h:1111:2: error: unknown type name 'u8'
u8 chunk_root_level;
^~
./usr/include/linux/btrfs_tree.h:1112:2: error: unknown type name 'u8'
u8 extent_root_level;
^~
./usr/include/linux/btrfs_tree.h:1113:2: error: unknown type name 'u8'
u8 fs_root_level;
^~
./usr/include/linux/btrfs_tree.h:1114:2: error: unknown type name 'u8'
u8 dev_root_level;
^~
./usr/include/linux/btrfs_tree.h:1115:2: error: unknown type name 'u8'
u8 csum_root_level;
^~
./usr/include/linux/btrfs_tree.h:1117:2: error: unknown type name 'u8'
u8 unused_8[10];
^~
./usr/include/linux/btrfs_tree.h:1133:2: error: unknown type name 'u8'
u8 csum[BTRFS_CSUM_SIZE];
^~
./usr/include/linux/btrfs_tree.h:1135:2: error: unknown type name 'u8'
u8 fsid[BTRFS_FSID_SIZE];
^~
./usr/include/linux/btrfs_tree.h:1162:2: error: unknown type name 'u8'
u8 root_level;
^~
./usr/include/linux/btrfs_tree.h:1163:2: error: unknown type name 'u8'
u8 chunk_root_level;
^~
./usr/include/linux/btrfs_tree.h:1164:2: error: unknown type name 'u8'
u8 log_root_level;
^~
./usr/include/linux/btrfs_tree.h:1173:2: error: unknown type name 'u8'
u8 metadata_uuid[BTRFS_FSID_SIZE];
^~
./usr/include/linux/btrfs_tree.h:1177:2: error: unknown type name 'u8'
u8 sys_chunk_array[BTRFS_SYSTEM_CHUNK_ARRAY_SIZE];
^~
./usr/include/linux/btrfs_tree.h:1268:2: error: unknown type name 'u8'
u8 csum[BTRFS_CSUM_SIZE];
^~
./usr/include/linux/btrfs_tree.h:1269:2: error: unknown type name 'u8'
u8 fsid[BTRFS_FSID_SIZE]; /* FS specific uuid */
^~
./usr/include/linux/btrfs_tree.h:1274:2: error: unknown type name 'u8'
u8 chunk_tree_uuid[BTRFS_UUID_SIZE];
^~
./usr/include/linux/btrfs_tree.h:1278:2: error: unknown type name 'u8'
u8 level;
^~
---
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: 33108 bytes --]
next prev parent reply other threads:[~2020-04-23 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 8:41 [PATCH v4 0/2] btrfs: Reformat and make btrfs_tree.h self-contained Qu Wenruo
2020-04-15 8:41 ` [PATCH v4 1/2] btrfs: Move on-disk structure definition to btrfs_tree.h Qu Wenruo
2020-04-21 11:31 ` Christoph Hellwig
2020-04-21 11:41 ` Qu Wenruo
2020-04-24 20:24 ` David Sterba
2020-04-25 7:14 ` Christoph Hellwig
2020-04-25 7:25 ` Qu Wenruo
2020-04-30 7:29 ` Qu Wenruo
2020-04-23 11:32 ` kbuild test robot [this message]
2020-04-15 8:41 ` [PATCH v4 2/2] btrfs: Reformat btrfs_tree.h comments Qu Wenruo
2020-04-16 10:20 ` David Sterba
2020-04-16 12:54 ` David Sterba
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=202004231935.sAvDUszh%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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).