[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202002280303.ERVhiFtH%lkp@intel.com>
Date: Fri, 28 Feb 2020 03:18:48 +0800
From: kbuild test robot <lkp@...el.com>
To: Ritesh Harjani <riteshh@...ux.ibm.com>
Cc: kbuild-all@...ts.01.org, jack@...e.cz, tytso@....edu,
linux-ext4@...r.kernel.org
Subject: Re: [PATCHv4 5/6] ext4: Move ext4_fiemap to use iomap framework.
Hi Ritesh,
I love your patch! Perhaps something to improve:
[auto build test WARNING on ext4/dev]
[also build test WARNING on linus/master v5.6-rc3 next-20200227]
[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/Ritesh-Harjani/ext4-bmap-fiemap-conversion-to-use-iomap/20200227-204414
base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-173-ge0787745-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@...el.com>
sparse warnings: (new ones prefixed by >>)
>> fs/ext4/extents.c:4918:24: sparse: sparse: symbol 'ext4_iomap_xattr_ops' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
Powered by blists - more mailing lists