From: Bruno Wolff III <bruno@wolff.to>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: akpm@linux-foundation.org, linux-embedded@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
phillip.lougher@gmail.com, tim.bird@am.sony.com
Subject: Re: [PATCH 0/9] Squashfs: Add support for LZMA compressed filesystems
Date: Mon, 21 Dec 2009 17:56:04 -0600 [thread overview]
Message-ID: <20091221235604.GA20459@wolff.to> (raw)
In-Reply-To: <4B300912.5060905@lougher.demon.co.uk>
On Mon, Dec 21, 2009 at 23:47:30 +0000,
Phillip Lougher <phillip@lougher.demon.co.uk> wrote:
> Bruno Wolff III wrote:
> >On Mon, Dec 07, 2009 at 08:37:48 +0000,
> > Phillip Lougher <phillip@lougher.demon.co.uk> wrote:
> >>Hi,
> >>
> >>The following patches add LZMA decompression support to Squashfs, using the
> >>in-kernel LZMA decompression library.
> >
> >Do these still have a chance to make 2.6.33?
> >
>
> It's very unlikely. Andrew wanted it to spend a cycle in linux-next. I'll then
> try for 2.6.34 merge. I'm happy with that.
I hadn't seen it show up there yet either. But maybe its a bit too early
for that. If it gets there I might have a chance of convincing one of
the Fedora kernel guys of back porting it, since F13 is likely to be released
with the 2,6,34 kernel in any case. (Along with some actual numbers for
our live iso images to show it's important to have. But I can get those
using the devel version of squashfs without the kernel changes.)
I'll keep an eye out for it showing up in linux-next. Thanks for the update.
next prev parent reply other threads:[~2009-12-21 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 8:37 [PATCH 0/9] Squashfs: Add support for LZMA compressed filesystems Phillip Lougher
2009-12-21 23:16 ` Bruno Wolff III
2009-12-21 23:47 ` Phillip Lougher
2009-12-21 23:56 ` Bruno Wolff III [this message]
2009-12-31 12:06 ` Bruno Wolff III
2010-01-01 9:11 ` Bruno Wolff III
-- strict thread matches above, loose matches on Subject: below --
2009-12-07 8:25 root
2009-12-07 8:47 ` Peter Korsgaard
2009-12-08 17:59 ` Phillip Lougher
2009-12-13 20:13 ` Arkadiusz Miśkiewicz
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=20091221235604.GA20459@wolff.to \
--to=bruno@wolff.to \
--cc=akpm@linux-foundation.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip.lougher@gmail.com \
--cc=phillip@lougher.demon.co.uk \
--cc=tim.bird@am.sony.com \
/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;
as well as URLs for NNTP newsgroup(s).