rcu: Remove SPARSE_RCU_POINTER Kconfig option
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Fri, 12 May 2017 22:56:35 +0000 (15:56 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Fri, 9 Jun 2017 01:52:41 +0000 (18:52 -0700)
commit41a2901e7d220875752a8c870e0b53288a578c20
tree7fee0c0fb4e4de059050c0003c370042bb832ffc
parentc4a09ff752e164c020bced6513e2008f992a02e6
rcu: Remove SPARSE_RCU_POINTER Kconfig option

The sparse-based checking for non-RCU accesses to RCU-protected pointers
has been around for a very long time, and it is now the only type of
sparse-based checking that is optional.  This commit therefore makes
it unconditional.

Reported-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>
Documentation/RCU/Design/Requirements/Requirements.html
Documentation/RCU/checklist.txt
Documentation/dev-tools/sparse.rst
include/linux/compiler.h
lib/Kconfig.debug
lib/Makefile
tools/testing/selftests/rcutorture/doc/TREE_RCU-kconfig.txt