From: Eric Biggers <ebiggers@kernel.org>
To: Nick Terrell <terrelln@fb.com>
Cc: "Nick Terrell" <nickrterrell@gmail.com>,
"squashfs-devel@lists.sourceforge.net"
<squashfs-devel@lists.sourceforge.net>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Christoph Hellwig" <hch@infradead.org>,
"Yann Collet" <cyan@fb.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"Petr Malat" <oss@malat.biz>, "Chris Mason" <clm@fb.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"Kernel Team" <Kernel-team@fb.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Niket Agarwal" <niketa@fb.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
"Johannes Weiner" <jweiner@fb.com>
Subject: Re: [f2fs-dev] [PATCH v7 0/3] Update to zstd-1.4.6
Date: Tue, 15 Dec 2020 16:00:30 -0800 [thread overview]
Message-ID: <X9lOHkAE67EP/sXo@sol.localdomain> (raw)
In-Reply-To: <DF6B2E26-2D6E-44FF-89DB-93A37E2EA268@fb.com>
On Tue, Dec 15, 2020 at 08:58:52PM +0000, Nick Terrell via Linux-f2fs-devel wrote:
>
>
> > On Dec 3, 2020, at 12:51 PM, Nick Terrell <nickrterrell@gmail.com> wrote:
> >
> > From: Nick Terrell <terrelln@fb.com>
> >
> > Please pull from
> >
> > git@github.com:terrelln/linux.git tags/v7-zstd-1.4.6
> >
> > to get these changes. Alternatively the patchset is included.
>
> Is it possible to get this patchset merged in the 5.11 merge window? It applies
> cleanly to the latest master. Please let me know if there is anything that I can do
> to drive this patchset towards merge.
>
> Thanks,
> Nick
Well, it's too late for 5.11 for patches that weren't already in linux-next, so
you'll have to aim for 5.12.
It looks like you're asking Herbert to pull this into the crypto tree? If he's
interested in doing that, that could work. However lib/zstd/ isn't that
strongly "crypto-related", and it doesn't actually have a maintainer listed in
MAINTAINERS. Perhaps another path forwards is for you to volunteer to maintain
lib/zstd/ and send pull requests for it directly to Linus?
- Eric
next prev parent reply other threads:[~2020-12-16 0:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 20:51 [PATCH v7 0/3] Update to zstd-1.4.6 Nick Terrell
2020-12-03 20:51 ` [PATCH v7 1/3] lib: zstd: Add kernel-specific API Nick Terrell
2020-12-03 20:51 ` [PATCH v7 2/3] lib: zstd: Add decompress_sources.h for decompress_unzstd Nick Terrell
2020-12-03 20:51 ` [PATCH v7 3/3] lib: zstd: Upgrade to latest upstream zstd version 1.4.6 Nick Terrell
2020-12-15 20:58 ` [PATCH v7 0/3] Update to zstd-1.4.6 Nick Terrell
2020-12-16 0:00 ` Eric Biggers [this message]
2020-12-16 0:48 ` [f2fs-dev] " Nick Terrell
2020-12-16 0:58 ` Herbert Xu
2020-12-16 1:12 ` Nick Terrell
2020-12-16 18:50 ` David Sterba
2020-12-16 22:07 ` Nick Terrell
2020-12-17 1:23 ` Michał Mirosław
2020-12-18 18:57 ` Nick Terrell
2021-02-27 9:33 ` Oleksandr Natalenko
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=X9lOHkAE67EP/sXo@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Kernel-team@fb.com \
--cc=clm@fb.com \
--cc=cyan@fb.com \
--cc=hch@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jweiner@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=nickrterrell@gmail.com \
--cc=niketa@fb.com \
--cc=oss@malat.biz \
--cc=squashfs-devel@lists.sourceforge.net \
--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).