public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>, Josh Boyer <jwboyer@gmail.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	dipankar@in.ibm.com, niv@us.ibm.com, manfred@colorfullife.com,
	peterz@infradead.org, lethal@linux-sh.org, kernel@wantstofly.org,
	kyle@mcmartin.ca, deller@gmx.de, davem@davemloft.net,
	ralf@linux-mips.org, jes@sgi.com, benh@kernel.crashing.org,
	paulus@samba.org, anton@samba.org
Subject: Re: [PATCH -tip] Convert CONFIG_SMP=y powerpc defconfigs to TREE_RCU.
Date: Sun, 5 Apr 2009 10:15:00 -0700	[thread overview]
Message-ID: <20090405171500.GL6893@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090405170113.GB17934@one.firstfloor.org>

On Sun, Apr 05, 2009 at 07:01:13PM +0200, Andi Kleen wrote:
> 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.

Good point!

							Thanx, Paul

  reply	other threads:[~2009-04-05 17:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3181463559098978317@unknownmsgid>
2009-04-04 13:21 ` [PATCH -tip] Convert CONFIG_SMP=y powerpc defconfigs to TREE_RCU Josh Boyer
2009-04-04 16:31   ` Paul E. McKenney
2009-04-05 10:17     ` Ingo Molnar
2009-04-05 10:37       ` Andi Kleen
2009-04-05 16:49         ` Paul E. McKenney
2009-04-05 17:01           ` Andi Kleen
2009-04-05 17:15             ` Paul E. McKenney [this message]
2009-04-05 16:44       ` Paul E. McKenney
2009-04-08 12:46         ` Ingo Molnar
2009-04-08 17:48           ` Paul E. McKenney
2009-04-08 18:10             ` Ingo Molnar
2009-04-08 18:27               ` Paul E. McKenney
2009-04-04  0:27 [PATCH -tip] Make TREE_RCU be default (was CLASSIC_RCU) Paul E. McKenney
2009-04-04  0:27 ` [PATCH -tip] Convert CONFIG_SMP=y powerpc defconfigs to TREE_RCU Paul E. McKenney

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=20090405171500.GL6893@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=dipankar@in.ibm.com \
    --cc=jes@sgi.com \
    --cc=jwboyer@gmail.com \
    --cc=kernel@wantstofly.org \
    --cc=kyle@mcmartin.ca \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=ralf@linux-mips.org \
    /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