[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090405170113.GB17934@one.firstfloor.org>
Date: Sun, 5 Apr 2009 19:01:13 +0200
From: Andi Kleen <andi@...stfloor.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
Josh Boyer <jwboyer@...il.com>, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, dipankar@...ibm.com, niv@...ibm.com,
manfred@...orfullife.com, peterz@...radead.org,
lethal@...ux-sh.org, kernel@...tstofly.org, kyle@...artin.ca,
deller@....de, davem@...emloft.net, ralf@...ux-mips.org,
jes@....com, benh@...nel.crashing.org, paulus@...ba.org,
anton@...ba.org
Subject: Re: [PATCH -tip] Convert CONFIG_SMP=y powerpc defconfigs to TREE_RCU.
On Sun, Apr 05, 2009 at 09:49:04AM -0700, Paul E. McKenney wrote:
> On Sun, Apr 05, 2009 at 12:37:59PM +0200, Andi Kleen wrote:
> > > I'd suggest you dont do these dozens of defconfig updates at all -
> > > arch maintainers can do this themselves, once the core kernel
> > > default has been flipped.
> >
> > AFAIK they don't. There's no make updatemyconfigwithdefaultstatementsconfig
>
> My guess is that I would in fact have to send a few patches. But I
> suppose that the real question is "how long should we wait to drop
> Classic RCU once the last arch has changed its defconfig?" I have
> been assuming that we would wait one release cycle.
I don't think you have to wait, stale entries in defconfigs happen
all the time and Kconfig just asks then.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
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