Hi Avri,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on scsi/for-next]
[also build test WARNING on next-20200515]
[cannot apply to mkp-scsi/for-next v5.7-rc5]
[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/Avri-Altman/scsi-ufs-Add-HPB-Sup...
base:
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-193-gb8fad4bc-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp(a)intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/scsi/ufs/ufshpb.c:35:26: sparse: sparse: symbol 'ufshpb_luns_conf' was
not declared. Should it be static?
drivers/scsi/ufs/ufshpb.c:36:19: sparse: sparse: symbol 'ufshpb_luns' was not
declared. Should it be static?
> drivers/scsi/ufs/ufshpb.c:40:6: sparse: sparse: symbol
'ufshpb_remove_lun' 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