From: David Sterba <dsterba@suse.cz>
To: Nick Terrell <terrelln@fb.com>
Cc: David Sterba <dsterba@suse.cz>,
kernel-team@fb.com, linux-btrfs@vger.kernel.org,
grub-devel@gnu.org
Subject: Re: [PATCH 0/3] btrfs: Add zstd support to btrfs
Date: Tue, 11 Sep 2018 12:23:40 +0200 [thread overview]
Message-ID: <20180911102340.GD24025@twin.jikos.cz> (raw)
In-Reply-To: <20180828013654.1627080-1-terrelln@fb.com>
On Mon, Aug 27, 2018 at 06:36:51PM -0700, Nick Terrell wrote:
> Hi all,
>
> This patch set imports the upstream kernel zstd library, patches it to work
> in grub, adds zstd support to the btrfs module, and adds a test case. I've
> separated the importing and patching of the upstream kernel zstd library
> for ease of review.
>
> Thanks to David Sterba for starting this project! I started my patch from
> where he left off.
The first patch did not make it to vger.kernel.org mailinglist, which
suggests that it's big, and possibly too big for merging. I did only a
prototype to make it work, I'm afraid the patch won't be accepted.
Your follow patches clean it up and IMHO go in the right direction, but
I think this needs to be done from the beginning.
next prev parent reply other threads:[~2018-09-11 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 1:36 [PATCH 0/3] btrfs: Add zstd support to btrfs Nick Terrell
2018-08-28 1:36 ` [PATCH 2/3] btrfs: Patch the kernel zstd Nick Terrell
2018-09-21 18:23 ` Daniel Kiper
2018-08-28 1:36 ` [PATCH 3/3] btrfs: Add zstd support to btrfs Nick Terrell
2018-09-21 18:29 ` Daniel Kiper
2018-09-11 10:23 ` David Sterba [this message]
2018-09-11 19:48 ` [PATCH 0/3] " Nick Terrell
[not found] ` <20180828013654.1627080-2-terrelln@fb.com>
2018-09-21 18:10 ` [PATCH 1/3] btrfs: Import kernel zstd Daniel Kiper
2018-09-21 18:48 ` Nick Terrell
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=20180911102340.GD24025@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=grub-devel@gnu.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=terrelln@fb.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).