[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201116165231.GA22834@infradead.org>
Date: Mon, 16 Nov 2020 16:52:31 +0000
From: Christoph Hellwig <hch@...radead.org>
To: Chris Mason <clm@...com>
Cc: Christoph Hellwig <hch@...radead.org>,
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>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v5 1/9] lib: zstd: Add zstd compatibility wrapper
On Tue, Nov 10, 2020 at 02:24:35PM -0500, Chris Mason wrote:
> I think APIs change based on the needs of the project. We do this all the
> time in the kernel, and we don???t think twice about updating users of the
> API as needed.
We update kernel APIs when:
- we need additional functionality
- thew new API is clearly better than the old one
None of that seems to be the case here.
Powered by blists - more mailing lists