From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Problems Implementing Snappy Patches
Date: Wed, 15 Feb 2012 23:03:30 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.02.15.23.03.29@cox.net> (raw)
In-Reply-To: CAKcLGm_AgoHWa1TGwxz6PfSkKvxmDXi_3ykHR10WgTFVW9Gt4g@mail.gmail.com
Mitch Harder posted on Wed, 15 Feb 2012 16:46:00 -0600 as excerpted:
> I've been trying to test the snappy compression patches, but I'm getting
> corruptions when trying to use snappy as built on my system.
>
> I'm checking out the Linux 3.2.6 kernel, merging that with the latest
> 'for-linus' branch on Chris Mason's kernel.org repo, and then
> integrating the snappy and lz4 patches from David Sterba's git
> repository (dev/compression-squad branch).
Given that we're past the 3.3 kernel merge window, wouldn't Chris's "for-
linus" branch be based on the patches that went into 3.3, now? IOW,
you're basing on 3.2.x but AFAIK you should be basing on 3.3, now, so
you're missing the 3.3 patches which CM's for-linus tree branch should be
assuming, at this point.
Unless you know otherwise of course. I run the mainline tree here, and
don't actually run anything btrfs yet, as once I started investigating I
realized that it's missing features (like multi-mirror not just dual-
mirror) that I need, and isn't yet as stable as I had hoped, either. So
I don't know that much about the specifics of CM's tree, but in the
general case, a for-linus branch would be based on 3.3 now, since it's
well past the merge window.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2012-02-15 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 22:46 Problems Implementing Snappy Patches Mitch Harder
2012-02-15 23:03 ` Duncan [this message]
2012-02-15 23:14 ` Mitch Harder
2012-02-16 2:06 ` Li Zefan
2012-02-16 13:01 ` Mitch Harder
2012-02-16 13:15 ` David Sterba
2012-02-17 0:10 ` Mitch Harder
2012-02-21 12:03 ` David Sterba
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=pan.2012.02.15.23.03.29@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).