From: Bruno Wolff III <bruno@wolff.to>
To: Phillip Lougher <phillip@squashfs.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Squashfs: add LZ4 compression
Date: Tue, 23 Jul 2013 10:10:09 -0500 [thread overview]
Message-ID: <20130723151009.GA5971@wolff.to> (raw)
In-Reply-To: <1374459663-15363-1-git-send-email-phillip@squashfs.org.uk>
On Mon, Jul 22, 2013 at 03:21:01 +0100,
Phillip Lougher <phillip@squashfs.org.uk> wrote:
>Hi
>
>Now that LZ4 compression support is in 3.11-rc1, I have written the
>following two patches for Squashfs to use it.
If this gets accepted are you going to move the LZ4 changes to squashfs-tools
into the stable branch? I'd like to make LZ4 work in mksquashfs in at least
rawhide once LZ4 is usable for squashfs file systems in the kernel. So I
was wondering whether to expect this to appear in stable shortly or to expect
to start doing builds using the master branch.
next prev parent reply other threads:[~2013-07-23 15:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 2:21 Phillip Lougher
2013-07-22 2:21 ` [PATCH 1/2] Squashfs: add LZ4 compression support Phillip Lougher
2013-07-22 4:35 ` Joe Perches
2013-07-22 2:21 ` [PATCH 2/2] Squashfs: Add LZ4 compression configuration option Phillip Lougher
2013-07-22 3:05 ` [PATCH 0/2] Squashfs: add LZ4 compression Gu Zheng
2013-07-22 5:07 ` Phillip Lougher
2013-07-22 6:04 ` Gu Zheng
2013-07-22 13:38 ` Phillip Lougher
2013-07-26 22:00 ` Rob Landley
2013-07-23 15:10 ` Bruno Wolff III [this message]
2013-07-23 16:17 ` Phillip Lougher
2013-07-23 16:29 ` Bruno Wolff III
2014-11-27 8:00 Phillip Lougher
2014-11-27 13:37 ` Bruno Wolff III
[not found] ` <CAJZww4gzTnbyB4jbFQc0N4G6GJ31pVwv-PNZtDMbUxXMoH-orQ@mail.gmail.com>
2014-11-27 16:55 ` Martin Vath
2014-12-12 7:44 ` Dave Vasilevsky
2014-12-12 8:31 ` Anthony F McInerney
2014-12-12 10:27 ` Guan Xin
[not found] ` <CAGw_SrN6tZyXRx6pxkpnhWc2U5845HRbfzhOK5v9qkjWejFpmA@mail.gmail.com>
2014-12-12 15:56 ` Bruno Wolff III
2014-12-12 22:45 ` Phillip Lougher
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=20130723151009.GA5971@wolff.to \
--to=bruno@wolff.to \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@squashfs.org.uk \
/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
Powered by JetHome