From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: Requirements and process
Date: Fri, 2 May 2008 23:35:19 -0700 [thread overview]
Message-ID: <20080502233519.a988b552.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080503154542.18807e59.sfr@canb.auug.org.au>
On Sat, 3 May 2008 15:45:42 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> The following architectures are not in linux-next (and should be):
>
> alpha cris frv
> h8300 m32r m68knommu
> mips mn10300 parisc
> um v850 xtensa
mips, m32r, parisc and xtensa do have git trees. The rest are mastered as
discrete patches in -mm.
Except for m68knommu, which pops unexpectedly out of the woodwork during
the merge window. I've asked that this be altered ;)
next prev parent reply other threads:[~2008-05-03 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 5:45 linux-next: Requirements and process Stephen Rothwell
2008-05-03 6:07 ` Stephen Rothwell
2008-07-22 22:31 ` Randy Dunlap
2008-07-23 4:28 ` Stephen Rothwell
2008-05-03 6:35 ` Andrew Morton [this message]
2008-05-03 7:45 ` Stephen Rothwell
2008-05-03 14:27 ` Andrew Morton
2008-07-23 4:41 ` Stephen Rothwell
2008-05-06 4:48 ` 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=20080502233519.a988b552.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 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.