From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [PATCH 5/5] btrfs: add preferred_metadata mode mount option
Date: Mon, 18 Jan 2021 06:56:14 +0800 [thread overview]
Message-ID: <202101180643.H7b13qb1-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3253 bytes --]
CC: kbuild-all(a)lists.01.org
In-Reply-To: <20210117185435.36263-6-kreijack@libero.it>
References: <20210117185435.36263-6-kreijack@libero.it>
TO: Goffredo Baroncelli <kreijack@libero.it>
TO: linux-btrfs(a)vger.kernel.org
CC: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
CC: Goffredo Baroncelli <kreijack@inwind.it>
Hi Goffredo,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on kdave/for-next]
[also build test WARNING on v5.11-rc3 next-20210115]
[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/Goffredo-Baroncelli/Add-an-ioctl-to-set-the-device-properties/20210118-035442
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
:::::: branch date: 3 hours ago
:::::: commit date: 3 hours ago
config: arm64-randconfig-s032-20210118 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-208-g46a52ca4-dirty
# https://github.com/0day-ci/linux/commit/6e3781fa16beb22201a3dac33326357fc0a0b7b9
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Goffredo-Baroncelli/Add-an-ioctl-to-set-the-device-properties/20210118-035442
git checkout 6e3781fa16beb22201a3dac33326357fc0a0b7b9
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
fs/btrfs/tests/btrfs-tests.c: note: in included file:
>> fs/btrfs/tests/../volumes.h:367:33: sparse: sparse: dubious one-bit signed bitfield
--
fs/btrfs/tests/inode-tests.c: note: in included file:
>> fs/btrfs/tests/../volumes.h:367:33: sparse: sparse: dubious one-bit signed bitfield
--
fs/btrfs/tests/extent-map-tests.c: note: in included file:
>> fs/btrfs/tests/../volumes.h:367:33: sparse: sparse: dubious one-bit signed bitfield
vim +367 fs/btrfs/tests/../volumes.h
cea9e4452ebaf18d Chris Mason 2008-04-09 361
b2117a39fa96cf48 Miao Xie 2011-01-05 362 struct btrfs_device_info {
b2117a39fa96cf48 Miao Xie 2011-01-05 363 struct btrfs_device *dev;
b2117a39fa96cf48 Miao Xie 2011-01-05 364 u64 dev_offset;
b2117a39fa96cf48 Miao Xie 2011-01-05 365 u64 max_avail;
73c5de0051533cbd Arne Jansen 2011-04-12 366 u64 total_avail;
6e3781fa16beb222 Goffredo Baroncelli 2021-01-17 @367 int preferred_metadata:1;
b2117a39fa96cf48 Miao Xie 2011-01-05 368 };
b2117a39fa96cf48 Miao Xie 2011-01-05 369
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 41661 bytes --]
next reply other threads:[~2021-01-17 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 22:56 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-17 18:54 [RFC][PATCH V5] btrfs: preferred_metadata: preferred device for metadata Goffredo Baroncelli
2021-01-17 18:54 ` [PATCH 5/5] btrfs: add preferred_metadata mode mount option Goffredo Baroncelli
2021-01-18 3:05 ` kernel test robot
2021-01-18 3:05 ` 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=202101180643.H7b13qb1-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.