rcu: Directly drive TASKS_RCU from Kconfig
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 20 Apr 2015 12:42:50 +0000 (05:42 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Wed, 27 May 2015 19:59:03 +0000 (12:59 -0700)
commit82d0f4c089991e6b302d961f0320282bf91652d7
tree1ba0f3bd15f4746888499523d86462f1ae054caf
parent0f41c0ddadfb3d5baffe62351c380e2881aacd58
rcu: Directly drive TASKS_RCU from Kconfig

Currently, Kconfig will ask the user whether TASKS_RCU 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 TASKS_RCU via "select" statements.  Which means that
as subsystems require TASKS_RCU, those subsystems will need to add
"select" statements of their own.

Reported-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Reviewed-by: Pranith Kumar <bobby.prani@gmail.com>
init/Kconfig
lib/Kconfig.debug
This page took 0.028485 seconds and 5 git commands to generate.