[linux-gfs2:for-next 2/2] fs/gfs2/glock.c:79:26: sparse: symbol 'ht_parms' was not declared. Should it be static?

[kbuild test robot]

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 for-next
head:   6afe4c76af372a6b453f33888e664beddc4647b4
commit: 6afe4c76af372a6b453f33888e664beddc4647b4 [2/2] GFS2: Use resizable hash table for glocks
reproduce:
  # apt-get install sparse
  git checkout 6afe4c76af372a6b453f33888e664beddc4647b4
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> fs/gfs2/glock.c:79:26: sparse: symbol 'ht_parms' was not declared. Should it be static?
   fs/gfs2/./trace_gfs2.h:160:1: sparse: odd constant _Bool cast (ffffffffffffffff becomes 1)
   fs/gfs2/glock.c:175:9: sparse: context imbalance in 'gfs2_glock_put' - unexpected unlock
   fs/gfs2/glock.c:1802:13: sparse: context imbalance in 'gfs2_glock_seq_start' - wrong count at exit
>> fs/gfs2/glock.c:1834:13: sparse: context imbalance in 'gfs2_glock_seq_stop' - unexpected unlock

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/