From: Andrew Morton <akpm@linux-foundation.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] m68knommu: ColdFire add support for kernel preemption
Date: Mon, 23 Jun 2008 10:42:04 -0700 [thread overview]
Message-ID: <20080623104204.4e5bcea0.akpm@linux-foundation.org> (raw)
In-Reply-To: <485FA3BC.5080807@snapgear.com>
On Mon, 23 Jun 2008 23:23:08 +1000 Greg Ungerer <gerg@snapgear.com> wrote:
> Do I need to send a request to Linus to pull this into his
> tree during the next merge window?
Yes, you do - nothing has changed in that regard.
> Or will it migrate up
> from linux-next?
Nope, linux-next is a testing tree only.
next prev parent reply other threads:[~2008-06-23 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 2:16 [PATCH] m68knommu: ColdFire add support for kernel preemption Greg Ungerer
2008-05-01 21:33 ` Andrew Morton
2008-05-02 7:19 ` Greg Ungerer
2008-05-02 8:37 ` Sebastian Siewior
2008-05-02 12:22 ` Andrew Morton
2008-06-23 5:32 ` Greg Ungerer
2008-06-23 5:51 ` Andrew Morton
2008-06-23 7:53 ` Stephen Rothwell
2008-06-23 13:23 ` Greg Ungerer
2008-06-23 17:42 ` Andrew Morton [this message]
2008-06-23 23:47 ` Stephen Rothwell
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=20080623104204.4e5bcea0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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