[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211113054140.GA20916@gondor.apana.org.au>
Date: Sat, 13 Nov 2021 13:41:40 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Nick Terrell <terrelln@...com>
Cc: nickrterrell@...il.com, torvalds@...ux-foundation.org,
sfr@...b.auug.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@...com, clm@...com,
oss@...at.biz, cyan@...com, hch@...radead.org,
mirq-linux@...e.qmqm.pl, dsterba@...e.cz, oleksandr@...alenko.name,
felixh@...com, ebiggers@...nel.org, rdunlap@...radead.org,
paul@...ljones.id.au, tseewald@...il.com, sedat.dilek@...il.com,
jd.girard@...nux.pf
Subject: Re: [GIT PULL] zstd changes for v5.16
Nick Terrell <terrelln@...com> wrote:
>
> 2. Reaching out to Herbert Xu—because the first zstd version went through the
> crypto tree—and other relevant maintainers who have been
> involved, and trying to get a word of support for adding me as the maintainer
> of lib/zstd in this thread.
Actually I don't think I ever merged lib/zstd. I did take
crypto/zstd though which is the Crypto API wrapper around the
lib/zstd code.
Since the current contention is with lib/zstd I think it probably
makes sense for Linus to take it directly.
I think you should certainly be the maintainer of lib/zstd since
it was added by you and mostly used by you too :)
Thanks,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists