linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Hugh Dickins <hughd@google.com>
Subject: Re: linux-next: Tree for Nov 14
Date: Tue, 13 Nov 2012 23:24:05 -0800	[thread overview]
Message-ID: <20121113232405.7dd4fe03.akpm@linux-foundation.org> (raw)
In-Reply-To: <20121114181536.3ec35e5ec622e7eaec791e00@canb.auug.org.au>

On Wed, 14 Nov 2012 18:15:36 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Andrew,
> 
> On Tue, 13 Nov 2012 22:56:35 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Wed, 14 Nov 2012 07:47:26 +0100 Ingo Molnar <mingo@kernel.org> wrote:
> > 
> > > * Andrew Morton <akpm@linux-foundation.org> wrote:
> > > 
> > > > It would help if the old sched/numa code wasn't in -next while 
> > > > you're away.  That would give me a clean run at 3.7 and will 
> > > > make it easier for others to integrate and test the four(!) 
> > > > different autoschednumacore implementations on top of 
> > > > linux-next.
> > > > 
> > > > Pretty please?
> > > 
> > > The next integration should have this solved: I have removed the 
> > > old sched/numa bits, replaced by the latest rebased/reworked 
> > > numa/core bits.
> > 
> > That solves one problem, but I still need to route around the numa
> > stuff when preparing the 3.8-rc1 merge.  Again!
> 
> I am not sure what is actually involved here, but would it help if I
> made you a new akpm-base with the old tip tree replaced by the new one
> that Ingo just pushed out?  Or are there still problematic things in the
> tip tree?

If this new code is targeted at 3.9 as I'm suggesting then it should go
into -next after 3.8-rc1, so the sched/numa part of -tip should be
omitted from -next until then.

If instead the plan is to merge it all into 3.8 then -tip should go
into -next as-is.

How's your crystal ball?

  reply	other threads:[~2012-11-14  7:24 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  5:30 linux-next: Tree for Nov 14 Stephen Rothwell
2012-11-14  5:37 ` Andrew Morton
2012-11-14  5:53   ` Andrew Morton
2012-11-14  6:47   ` Ingo Molnar
2012-11-14  6:56     ` Andrew Morton
2012-11-14  7:15       ` Stephen Rothwell
2012-11-14  7:24         ` Andrew Morton [this message]
2012-11-14  7:39       ` Ingo Molnar
2012-11-14  8:13         ` Hugh Dickins
2012-11-14 17:05           ` Rik van Riel
2012-11-15 12:10             ` Mel Gorman
2012-11-14 17:19       ` Linus Torvalds
2012-11-14  6:55   ` Stephen Rothwell
2012-11-14  7:03     ` Stephen Rothwell
2012-11-14 19:41 ` linux-next: Tree for Nov 14 (gpu/drm/i915) Randy Dunlap
2012-11-14 20:17   ` Andrew Morton
2012-11-15  0:59 ` [PATCH 1/2] asm-generic: add __WARN() to bug.h Randy Dunlap
2012-11-15  1:28   ` David Rientjes
2012-11-15  0:59 ` [PATCH 2/2] mm: balloon_compaction.c needs asm-generic/bug.h Randy Dunlap
2012-11-15  1:29   ` David Rientjes
2012-11-15  1:29     ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2023-11-14  3:19 linux-next: Tree for Nov 14 Stephen Rothwell
2022-11-14  7:49 Stephen Rothwell
2019-11-14  8:31 Stephen Rothwell
2019-11-14 18:38 ` Naresh Kamboju
2019-11-14 20:11   ` Jan Stancek
2019-11-14 21:19     ` Arnd Bergmann
2018-11-14  5:26 Stephen Rothwell
2017-11-14  6:20 Stephen Rothwell
2016-11-14  7:23 Stephen Rothwell
2014-11-14  8:27 Stephen Rothwell
2014-11-15 21:19 ` Guenter Roeck
2014-11-16  2:33   ` Jiang Liu
2014-11-16  3:22     ` Guenter Roeck
2014-11-16  4:20       ` Jiang Liu
2014-11-16  6:56         ` Guenter Roeck
2014-11-16  8:24           ` Jiang Liu
2014-11-16  8:37             ` Jiang Liu
2014-11-16 15:42               ` Guenter Roeck
2014-11-16 16:01             ` Guenter Roeck
2014-11-16 16:11               ` Guenter Roeck
2014-11-17  5:12       ` Jiang Liu
2014-11-17 17:02         ` Guenter Roeck
2013-11-14  4:22 Stephen Rothwell
2011-11-14  3:43 Stephen Rothwell
2019-11-14 16:43 ` Christian Brauner

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=20121113232405.7dd4fe03.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).