From: kernel test robot <lkp@intel.com>
To: Johannes Thumshirn <jth@kernel.org>,
Chris Mason <chris.mason@fusionio.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Filipe Manana <fdmanana@suse.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:BTRFS FILE SYSTEM" <linux-btrfs@vger.kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] btrfs: tests: add selftests for RAID stripe-tree
Date: Tue, 1 Oct 2024 05:27:43 +0800 [thread overview]
Message-ID: <202410010421.NzGgvE6Y-lkp@intel.com> (raw)
In-Reply-To: <20240930104054.12290-1-jth@kernel.org>
Hi Johannes,
kernel test robot noticed the following build warnings:
[auto build test WARNING on kdave/for-next]
[also build test WARNING on linus/master v6.12-rc1 next-20240930]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Johannes-Thumshirn/btrfs-tests-add-selftests-for-RAID-stripe-tree/20240930-184234
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link: https://lore.kernel.org/r/20240930104054.12290-1-jth%40kernel.org
patch subject: [PATCH] btrfs: tests: add selftests for RAID stripe-tree
config: i386-buildonly-randconfig-004-20241001 (https://download.01.org/0day-ci/archive/20241001/202410010421.NzGgvE6Y-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241001/202410010421.NzGgvE6Y-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202410010421.NzGgvE6Y-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/btrfs/ioctl.c:37:
>> fs/btrfs/volumes.h:837:5: warning: "CONFIG_BTRFS_FS_RUN_SANITY_TESTS" is not defined, evaluates to 0 [-Wundef]
837 | #if CONFIG_BTRFS_FS_RUN_SANITY_TESTS
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
In file included from fs/btrfs/relocation.c:16:
>> fs/btrfs/volumes.h:837:5: warning: "CONFIG_BTRFS_FS_RUN_SANITY_TESTS" is not defined, evaluates to 0 [-Wundef]
837 | #if CONFIG_BTRFS_FS_RUN_SANITY_TESTS
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/btrfs/relocation.c:39:
>> fs/btrfs/raid-stripe-tree.h:31:5: warning: "CONFIG_BTRFS_FS_RUN_SANITY_TESTS" is not defined, evaluates to 0 [-Wundef]
31 | #if CONFIG_BTRFS_FS_RUN_SANITY_TESTS
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
In file included from fs/btrfs/raid-stripe-tree.c:12:
>> fs/btrfs/raid-stripe-tree.h:31:5: warning: "CONFIG_BTRFS_FS_RUN_SANITY_TESTS" is not defined, evaluates to 0 [-Wundef]
31 | #if CONFIG_BTRFS_FS_RUN_SANITY_TESTS
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/btrfs/raid-stripe-tree.c:13:
>> fs/btrfs/volumes.h:837:5: warning: "CONFIG_BTRFS_FS_RUN_SANITY_TESTS" is not defined, evaluates to 0 [-Wundef]
837 | #if CONFIG_BTRFS_FS_RUN_SANITY_TESTS
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/CONFIG_BTRFS_FS_RUN_SANITY_TESTS +837 fs/btrfs/volumes.h
836
> 837 #if CONFIG_BTRFS_FS_RUN_SANITY_TESTS
838 struct btrfs_io_context *alloc_btrfs_io_context(struct btrfs_fs_info *fs_info,
839 u64 logical, u16 total_stripes);
840 #endif
841
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-30 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 10:40 [PATCH] btrfs: tests: add selftests for RAID stripe-tree Johannes Thumshirn
2024-09-30 21:27 ` kernel test robot [this message]
2024-10-01 1:11 ` kernel 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=202410010421.NzGgvE6Y-lkp@intel.com \
--to=lkp@intel.com \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=jth@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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).