[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 3 Mar 2008 10:55:11 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Roman Zippel <zippel@...ux-m68k.org>
Cc: ego@...ibm.com, linux-kernel@...r.kernel.org,
linux-rt-users@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Steven Rostedt <rostedt@...dmis.org>,
Dipankar Sarma <dipankar@...ibm.com>,
Ted Tso <tytso@...ibm.com>, dvhltc@...ibm.com,
Oleg Nesterov <oleg@...sign.ru>,
Andrew Morton <akpm@...ux-foundation.org>, bunk@...nel.org,
Josh Triplett <josh@...edesktop.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [RFC PATCH 4/6] Preempt-RCU: Implementation
On Sun, Mar 02, 2008 at 04:06:10AM +0100, Roman Zippel wrote:
> Hi,
>
> On Sat, 1 Mar 2008, Paul E. McKenney wrote:
>
> > Is this what you had in mind? I don't have any way to test on a
> > system not supporting CONFIG_PREEMPT, but seems to work on x86.
>
> Yes, looks fine.
>
> > +config PREEMPT_RCU
> > + bool "Preemptible RCU"
> > + depends on PREEMPT
> > + default n
>
> "default n" isn't really necessary, it's already the default.
Fair enough. But something like 125 Kconfig files in 2.6.25-rc3 have
at least one "default n" in them, so is it worth getting rid of it?
Seems to me that the explicit "default n" has some substantial readability
advantages.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists