From: Chris Mason <clm@fb.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Nick Terrell <terrelln@fb.com>,
Phillip Lougher <phillip@squashfs.org.uk>,
Sean Purcell <me@seanp.xyz>, David Sterba <dsterba@suse.cz>
Subject: Re: [GIT PULL] zstd support (lib, btrfs, squashfs)
Date: Fri, 8 Sep 2017 22:19:22 -0400 [thread overview]
Message-ID: <20170909021921.GA25782@clm-mbp.thefacebook.com> (raw)
In-Reply-To: <20170909013559.GA29188@gondor.apana.org.au>
On Sat, Sep 09, 2017 at 09:35:59AM +0800, Herbert Xu wrote:
>On Fri, Sep 08, 2017 at 03:33:05PM -0400, Chris Mason wrote:
>>
>> crypto/Kconfig | 9 +
>> crypto/Makefile | 1 +
>> crypto/testmgr.c | 10 +
>> crypto/testmgr.h | 71 +
>> crypto/zstd.c | 265 ++++
>
>Is there anyone going to use zstd through the crypto API? If not
>then I don't see the point in adding it at this point. Especially
>as the compression API is still in a state of flux.
That part was requested by intel, but I'm happy to leave it out for
another time. The rest of the patch series doesn't depend on it at all.
-chris
next prev parent reply other threads:[~2017-09-09 2:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 19:33 Chris Mason
2017-09-09 0:43 ` Chris Mason
2017-09-09 1:35 ` Herbert Xu
2017-09-09 2:19 ` Chris Mason [this message]
2017-09-09 2:48 ` Nick Terrell
2017-09-09 4:14 ` Herbert Xu
2017-09-11 19:24 ` [GIT PULL v2] zstd support (lib, btrfs, squashfs, nocrypto) Chris Mason
2017-09-12 6:30 ` 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=20170909021921.GA25782@clm-mbp.thefacebook.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=herbert@gondor.apana.org.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@seanp.xyz \
--cc=phillip@squashfs.org.uk \
--cc=terrelln@fb.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®