[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201803161633.LJb0owl8%fengguang.wu@intel.com>
Date: Fri, 16 Mar 2018 16:15:33 +0800
From: kbuild test robot <fengguang.wu@...el.com>
To: Martin Brandenburg <martin@...ibond.com>
Cc: kbuild-all@...org, Mike Marshall <hubcap@...ibond.com>,
devel@...ts.orangefs.org, linux-kernel@...r.kernel.org
Subject: [martinbrandenburg:for-next 20/24] fs/orangefs/file.c:586:5: sparse:
symbol 'orangefs_flush' was not declared. Should it be static?
tree: https://github.com/martinbrandenburg/linux for-next
head: f73753424e408389a77bcfa9b04beb41f0f6b2f8
commit: 27dd09ddfeca4937da105e89ded1ba3d35e1038e [20/24] orangefs: implement writepage
reproduce:
# apt-get install sparse
git checkout 27dd09ddfeca4937da105e89ded1ba3d35e1038e
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
fs/orangefs/file.c:428:35: sparse: symbol 'orangefs_file_vm_ops' was not declared. Should it be static?
>> fs/orangefs/file.c:586:5: sparse: symbol 'orangefs_flush' was not declared. Should it be static?
--
>> fs/orangefs/inode.c:88:5: sparse: symbol 'orangefs_write_end' 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/pipermail/kbuild-all Intel Corporation
Powered by blists - more mailing lists