From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, tglx@linutronix.de, hpa@zytor.com
Subject: Re: [v2.6.26] what's brewing in x86.git for v2.6.26
Date: Thu, 17 Apr 2008 02:33:31 -0700 [thread overview]
Message-ID: <20080417023331.3350e217.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080417.021935.170766914.davem@davemloft.net>
On Thu, 17 Apr 2008 02:19:35 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Thu, 17 Apr 2008 01:54:25 -0700
>
> > linux-next ramped up across the 2.6.25-rc window and I wanted to give it
> > some time to see how it would pan out.
> ...
> > I don't know what you mena by this. But linux-next integrates only the
> > other subsystem trees and they have rarely caused me integration problems
> > against git-net.
There are maybe as many as 100 "subsystem trees" hosted in -mm. Stuff like
md, ipmi, tty, elf, keys, procfs, char drivers, nbd, fbdev, aoe, fuse, edac
and the list goes on.
Once I get -mm based on linux-next, the next step is to somehow feed those
trees (well, the "stable" parts thereof) back into linux-next while not
losing track of all the patches. I haven't a clue how I'll do this ;)
But I haven't thought about it much yet.
next prev parent reply other threads:[~2008-04-17 10:00 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 20:23 [v2.6.26] what's brewing in x86.git for v2.6.26 Ingo Molnar
2008-04-16 20:37 ` Roland Dreier
2008-04-16 22:18 ` Suresh Siddha
2008-04-16 20:50 ` Andi Kleen
2008-04-17 10:06 ` Alexander van Heukelum
2008-04-17 10:51 ` Andi Kleen
2008-04-17 13:33 ` Alexander van Heukelum
2008-04-18 8:38 ` Ingo Molnar
2008-04-18 10:51 ` Andi Kleen
2008-04-17 7:25 ` Andrew Morton
2008-04-17 7:45 ` Pekka Enberg
2008-04-17 8:20 ` Andrew Morton
2008-04-17 8:32 ` Pekka J Enberg
2008-04-17 8:34 ` Pekka Enberg
2008-04-17 8:40 ` Ingo Molnar
2008-04-17 8:42 ` Andrew Morton
2008-04-17 11:49 ` Christoph Hellwig
2008-04-17 11:56 ` Ingo Molnar
2008-04-17 18:01 ` Andrew Morton
2008-04-17 18:51 ` Ingo Molnar
2008-04-17 19:57 ` Andrew Morton
2008-04-17 20:18 ` Ingo Molnar
2008-04-18 9:33 ` Tomasz Kłoczko
2008-04-18 9:42 ` Ingo Molnar
2008-04-17 8:14 ` Andrew Morton
2008-04-17 8:57 ` Avi Kivity
2008-04-17 10:32 ` Johannes Weiner
2008-04-17 10:50 ` Andrew Morton
2008-04-17 11:49 ` Christoph Hellwig
2008-04-17 17:36 ` Andrew Morton
2008-04-17 8:30 ` Ingo Molnar
2008-04-17 8:40 ` Andrew Morton
2008-04-17 8:45 ` David Miller
2008-04-17 8:54 ` Andrew Morton
2008-04-17 8:56 ` Andrew Morton
2008-04-17 9:19 ` David Miller
2008-04-17 9:33 ` Andrew Morton [this message]
2008-04-17 9:06 ` Ingo Molnar
2008-04-17 9:18 ` Andrew Morton
2008-04-17 9:30 ` Ingo Molnar
2008-04-17 9:36 ` Andrew Morton
2008-04-17 9:46 ` Ingo Molnar
2008-04-17 10:06 ` Andrew Morton
2008-04-17 10:11 ` Andi Kleen
2008-04-17 10:18 ` Andrew Morton
2008-04-17 10:29 ` Andi Kleen
2008-04-17 10:19 ` Pekka Enberg
2008-04-17 10:33 ` Andrew Morton
2008-04-17 10:38 ` Ingo Molnar
2008-04-17 10:42 ` Pekka Enberg
2008-04-18 11:12 ` Nick Piggin
2008-04-17 14:01 ` Arjan van de Ven
2008-04-17 15:26 ` Ingo Molnar
2008-04-18 12:41 ` Ingo Molnar
2008-04-17 10:41 ` Pekka Enberg
2008-04-17 18:47 ` Vegard Nossum
2008-04-17 19:27 ` Ingo Molnar
2008-04-17 19:35 ` Ingo Molnar
2008-04-17 19:39 ` Vegard Nossum
2008-04-17 19:43 ` Andrew Morton
2008-04-17 20:39 ` Vegard Nossum
2008-04-17 20:55 ` Andrew Morton
2008-04-17 9:53 ` Andrew Morton
2008-04-17 7:48 ` Andrew Morton
2008-04-18 6:27 ` Andrew Morton
2008-04-18 6:38 ` David Miller
2008-04-18 7:47 ` Ingo Molnar
2008-04-18 8:00 ` Andrew Morton
2008-04-18 8:11 ` Christoph Hellwig
2008-04-18 8:18 ` David Miller
2008-04-18 12:48 ` Ingo Molnar
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=20080417023331.3350e217.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.