rcu: Directly drive RCU_USER_QS from Kconfig
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 20 Apr 2015 13:17:15 +0000 (06:17 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Wed, 27 May 2015 19:59:03 +0000 (12:59 -0700)
Currently, Kconfig will ask the user whether RCU_USER_QS should be set.
This is silly because Kconfig already has all the information that it
needs to set this parameter.  This commit therefore directly drives
the value of RCU_USER_QS via NO_HZ_FULL's "select" statement.

Reported-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Pranith Kumar <bobby.prani@gmail.com>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
init/Kconfig

diff --cc init/Kconfig
Simple merge