[dgc-xfs:fallocate-insert-range 10/10] fs/xfs/xfs_bmap_util.c:1387:1: sparse: symbol 'xfs_shift_file_space' was not declared. Should it be static?

[dgc-xfs:fallocate-insert-range 10/10] fs/xfs/xfs_bmap_util.c:1387:1: sparse: symbol 'xfs_shift_file_space' was not declared. Should it be static?

[kbuild test robot]

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs fallocate-insert-range
head:   a904b1ca5751faf5ece8600e18cd3b674afcca1b
commit: a904b1ca5751faf5ece8600e18cd3b674afcca1b [10/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate
reproduce:
  # apt-get install sparse
  git checkout a904b1ca5751faf5ece8600e18cd3b674afcca1b
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> fs/xfs/xfs_bmap_util.c:1387:1: sparse: symbol 'xfs_shift_file_space' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

[PATCH dgc-xfs] xfs: xfs_shift_file_space can be static

[kbuild test robot]

Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
 xfs_bmap_util.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
index fe1f11b..e867573 100644
--- a/fs/xfs/xfs_bmap_util.c
+++ b/fs/xfs/xfs_bmap_util.c
@@ -1383,7 +1383,7 @@ out:
  * If we are shifting right, we will start with last extent inside file space
  * and continue until we reach the block corresponding to offset.
  */
-int
+static int
 xfs_shift_file_space(
 	struct xfs_inode        *ip,
 	xfs_off_t               offset,