From: Andrew Morton <akpm@linux-foundation.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: sfr@canb.auug.org.au, philipp.zabel@gmail.com,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: linux-next: Linus' tree build breakage
Date: Tue, 22 Apr 2008 06:58:49 -0700 [thread overview]
Message-ID: <20080422065849.d0b248e8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080422073622.GB22955@flint.arm.linux.org.uk>
> On Tue, 22 Apr 2008 08:36:22 +0100 Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> linux-next will not give me anything which -mm isn't giving me. As I
> said in the discussion, linux-next value is _very_ small for me.
Putting arm into linux-next means that Stephen (and git) handle the merges
rather than having me (and not-git) do it. Which helps me.
I expect that linux-next will get a lot more cross-compilation testing than
-mm. Which helps you.
next prev parent reply other threads:[~2008-04-22 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 0:31 linux-next: Linus' tree build breakage Stephen Rothwell
2008-04-22 7:36 ` Russell King
2008-04-22 7:43 ` David Miller
2008-04-22 13:58 ` Andrew Morton [this message]
2008-04-22 15:04 ` Stephen Rothwell
2008-04-22 22:30 ` Greg KH
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=20080422065849.d0b248e8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=philipp.zabel@gmail.com \
--cc=rmk+lkml@arm.linux.org.uk \
--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 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.