[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <202001312114.IkYUPqKR%lkp@intel.com>
Date: Fri, 31 Jan 2020 21:04:20 +0800
From: kbuild test robot <lkp@...el.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: kbuild-all@...ts.01.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [linux-next:master 4531/12088] fs/fs_parser.c:191:5: sparse: sparse:
symbol 'fs_param_bad_value' was not declared. Should it be static?
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c8e31a0fc39797784e4b9acae3bd2e0c7bade36e
commit: 2552e0ea2d71360b76faf1cd4ffb58019c92f817 [4531/12088] turn fs_param_is_... into functions
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-154-g1dc00f87-dirty
git checkout 2552e0ea2d71360b76faf1cd4ffb58019c92f817
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/fs_parser.c:191:5: sparse: sparse: symbol 'fs_param_bad_value' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
Powered by blists - more mailing lists