From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: rcu: Make a seperate Kconfig menu for RCU
Date: Wed, 7 Jan 2009 22:51:46 +0530 [thread overview]
Message-ID: <20090107172146.GB4145@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090107171851.GC6900@linux.vnet.ibm.com>
On Wed, Jan 07, 2009 at 09:18:51AM -0800, Paul E. McKenney wrote:
> On Wed, Jan 07, 2009 at 10:40:17PM +0530, Dhaval Giani wrote:
> > Hi Paul, Ingo,
> >
> > On selecting tree RCU, there are a total of 4 different RCU Kconfig options.
> > Maybe its time to give RCU a menu of its own.
>
> Looks good to me!
>
> Reviewed-by: Paul E. McKenneyh <paulmck@linux.vnet.ibm.com>
>
> > Signed-off-by: Dhaval Giani <dhaval@linux.vnet.ibm.com>
> >
And I messed up Ingo's email address in the initial post. Correcting it!
> > ---
> > init/Kconfig | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > Index: linux-2.6/init/Kconfig
> > ===================================================================
> > --- linux-2.6.orig/init/Kconfig 2009-01-07 10:18:17.000000000 +0530
> > +++ linux-2.6/init/Kconfig 2009-01-07 21:01:39.000000000 +0530
> > @@ -945,6 +945,8 @@ source "block/Kconfig"
> > config PREEMPT_NOTIFIERS
> > bool
> >
> > +menu "RCU related options"
> > +
> > choice
> > prompt "RCU Implementation"
> > default CLASSIC_RCU
> > @@ -1032,3 +1034,5 @@ config PREEMPT_RCU_TRACE
> > help
> > This option provides tracing for the PREEMPT_RCU implementation,
> > permitting Makefile to trivially select kernel/rcupreempt_trace.c.
> > +
> > +endmenu
--
regards,
Dhaval
prev parent reply other threads:[~2009-01-07 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 17:10 rcu: Make a seperate Kconfig menu for RCU Dhaval Giani
2009-01-07 17:18 ` Paul E. McKenney
2009-01-07 17:21 ` Dhaval Giani [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090107172146.GB4145@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox