[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CCDAB4AB-DE8D-4ADE-9221-02AE732CBAE2@fb.com>
Date: Wed, 16 Sep 2020 10:20:52 -0400
From: "Chris Mason" <clm@...com>
To: Christoph Hellwig <hch@...radead.org>
CC: Nick Terrell <nickrterrell@...il.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
<linux-crypto@...r.kernel.org>, <linux-btrfs@...r.kernel.org>,
<squashfs-devel@...ts.sourceforge.net>,
<linux-f2fs-devel@...ts.sourceforge.net>,
<linux-kernel@...r.kernel.org>, Kernel Team <Kernel-team@...com>,
Nick Terrell <terrelln@...com>, Petr Malat <oss@...at.biz>,
Johannes Weiner <jweiner@...com>,
Niket Agarwal <niketa@...com>, Yann Collet <cyan@...com>
Subject: Re: [PATCH 5/9] btrfs: zstd: Switch to the zstd-1.4.6 API
On 16 Sep 2020, at 4:49, Christoph Hellwig wrote:
> On Tue, Sep 15, 2020 at 08:42:59PM -0700, Nick Terrell wrote:
>> From: Nick Terrell <terrelln@...com>
>>
>> Move away from the compatibility wrapper to the zstd-1.4.6 API. This
>> code is functionally equivalent.
>
> Again, please use sensible names And no one gives a fuck if this bad
> API is "zstd-1.4.6" as the Linux kernel uses its own APIs, not some
> random mess from a badly written userspace package.
Hi Christoph,
It’s not completely clear what you’re asking for here. If the API
matches what’s in zstd-1.4.6, that seems like a reasonable way to
label it. That’s what the upstream is for this code.
I’m also not sure why we’re taking extra time to shit on the zstd
userspace package. Can we please be constructive or at least
actionable?
-chris
Powered by blists - more mailing lists