public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [PATCH 2/2] btrfs: move btrfs_super_block to uapi/linux/btrfs_tree.h
Date: Mon, 8 Nov 2021 07:24:49 +0800	[thread overview]
Message-ID: <202111080733.t3eVhOAe-lkp@intel.com> (raw)
In-Reply-To: <20211019112925.71920-3-wqu@suse.com>

[-- Attachment #1: Type: text/plain, Size: 3553 bytes --]

Hi Qu,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on kdave/for-next]
[also build test ERROR on v5.15]
[cannot apply to next-20211106]
[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/Qu-Wenruo/btrfs-cleanup-on-btrfs_super_block-definition/20211019-193103
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
config: i386-randconfig-c001-20211019 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 9660563950aaed54020bfdf0be07e7096a9553e4)
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
        # https://github.com/0day-ci/linux/commit/5207fb0ee3a623a1069a84661bf6b41104c468e5
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Qu-Wenruo/btrfs-cleanup-on-btrfs_super_block-definition/20211019-193103
        git checkout 5207fb0ee3a623a1069a84661bf6b41104c468e5
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

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/btrfs_tree.h:519:2: error: unknown type name 'u8'
           u8 tree_root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:520:2: error: unknown type name 'u8'
           u8 chunk_root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:521:2: error: unknown type name 'u8'
           u8 extent_root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:522:2: error: unknown type name 'u8'
           u8 fs_root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:523:2: error: unknown type name 'u8'
           u8 dev_root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:524:2: error: unknown type name 'u8'
           u8 csum_root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:526:2: error: unknown type name 'u8'
           u8 unused_8[10];
           ^
   ./usr/include/linux/btrfs_tree.h:579:2: error: unknown type name 'u8'
           u8 csum[BTRFS_CSUM_SIZE];
           ^
   ./usr/include/linux/btrfs_tree.h:581:2: error: unknown type name 'u8'
           u8 fsid[BTRFS_FSID_SIZE];
           ^
   ./usr/include/linux/btrfs_tree.h:609:2: error: unknown type name 'u8'
           u8 root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:610:2: error: unknown type name 'u8'
           u8 chunk_root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:611:2: error: unknown type name 'u8'
           u8 log_root_level;
           ^
   ./usr/include/linux/btrfs_tree.h:620:2: error: unknown type name 'u8'
           u8 metadata_uuid[BTRFS_FSID_SIZE];
           ^
   ./usr/include/linux/btrfs_tree.h:624:2: error: unknown type name 'u8'
           u8 sys_chunk_array[BTRFS_SYSTEM_CHUNK_ARRAY_SIZE];
           ^
   ./usr/include/linux/btrfs_tree.h:628:2: error: unknown type name 'u8'
           u8 padding[565];
           ^
   15 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: 28932 bytes --]

  parent reply	other threads:[~2021-11-07 23:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 11:29 [PATCH 0/2] btrfs: cleanup on btrfs_super_block definition Qu Wenruo
2021-10-19 11:29 ` [PATCH 1/2] btrfs: make sizeof(struct btrfs_super_block) to match BTRFS_SUPER_INFO_SIZE Qu Wenruo
2021-10-19 15:46   ` David Sterba
2021-10-19 11:29 ` [PATCH 2/2] btrfs: move btrfs_super_block to uapi/linux/btrfs_tree.h Qu Wenruo
2021-10-19 16:10   ` David Sterba
2021-10-20  0:19     ` Qu Wenruo
2021-10-20 17:13       ` David Sterba
2021-10-20 23:18         ` Qu Wenruo
2021-11-07 23:24   ` kernel test robot [this message]
2021-10-19 14:08 ` [PATCH 0/2] btrfs: cleanup on btrfs_super_block definition Josef Bacik

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=202111080733.t3eVhOAe-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --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