From 41278654b8cde6e850694a4b221882477d8e95bf Mon Sep 17 00:00:00 2001 From: Paul Gortmaker Date: Wed, 24 Oct 2012 11:07:09 -0700 Subject: [PATCH] --- yaml --- r: 338838 b: refs/heads/master c: af71befa282ddf51c09509978abe1e83de8fe7eb h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/init/Kconfig | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index 98ddce7483b9..fff92d8c8bf2 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 340f588bbaed6cb518aa65e7a330dcc3fff911f8 +refs/heads/master: af71befa282ddf51c09509978abe1e83de8fe7eb diff --git a/trunk/init/Kconfig b/trunk/init/Kconfig index b63e7982c1c6..ec62139207d3 100644 --- a/trunk/init/Kconfig +++ b/trunk/init/Kconfig @@ -494,11 +494,11 @@ config RCU_USER_QS puts RCU in extended quiescent state when the CPU runs in userspace. It means that when a CPU runs in userspace, it is excluded from the global RCU state machine and thus doesn't - to keep the timer tick on for RCU. + try to keep the timer tick on for RCU. Unless you want to hack and help the development of the full - tickless feature, you shouldn't enable this option. It adds - unnecessary overhead. + tickless feature, you shouldn't enable this option. It also + adds unnecessary overhead. If unsure say N