From: "H. Peter Anvin" <hpa@zytor.com>
To: Alain Knaff <alain@knaff.lu>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Russell King <rmk@arm.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] bzip2/lzma kernel compression
Date: Sat, 10 Jan 2009 16:33:52 -0800 [thread overview]
Message-ID: <49693E70.4050303@zytor.com> (raw)
In-Reply-To: <4968A737.7040909@knaff.lu>
Alain Knaff wrote:
>
> But now I am curious how this will evolve from here. I suppose it will
> soon appear in one of the patch-2.6.28-gitxy.gz under
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots , and then in an
> 2.6.29-rcx etc.
> Or are there some more other steps involved in between?
>
Well, Linus opted not to merge it for 2.6.29-rc1, which means it is dead
for this merge cycle. This gives us a couple of options, with the aim
to get it merged into 2.6.30:
- We can continue to carry it in the -tip tree, which also means it will
be in the linux-next tree.
- We can push it to Andrew Morton for the -mm tree.
- Sam could take it in his kbuild tree.
Out of these, I think the kbuild tree is entirely inappropriate. The
selection of the other two is mostly a matter of testing, and which way
will be easier to add the ARM code and other arch support.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-01-11 0:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 18:45 [GIT PULL] bzip2/lzma kernel compression H. Peter Anvin
2009-01-09 20:52 ` Yinghai Lu
2009-01-09 21:43 ` Yinghai Lu
2009-01-11 2:47 ` Ingo Molnar
2009-01-11 2:50 ` H. Peter Anvin
2009-01-11 7:07 ` Yinghai Lu
[not found] ` <4968A737.7040909@knaff.lu>
2009-01-11 0:33 ` H. Peter Anvin [this message]
2009-01-11 7:01 ` Alain Knaff
-- strict thread matches above, loose matches on Subject: below --
2009-01-15 13:19 Etienne Lorrain
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=49693E70.4050303@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=alain@knaff.lu \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sam@ravnborg.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