From: Nick Terrell <terrelln@fb.com>
To: "B093B859-53CC-4818-8CC3-A317F4872AD6@fb.com"
<B093B859-53CC-4818-8CC3-A317F4872AD6@fb.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL][PATCH v11 0/4] Update to zstd-1.4.10
Date: Wed, 29 Sep 2021 01:30:26 +0000 [thread overview]
Message-ID: <4A374EA5-F4CC-4C41-A810-90D09CB7A5FB@fb.com> (raw)
In-Reply-To: <e19ebd67-949d-e43c-4090-ab1ceadcdfab@gmail.com>
> On Sep 28, 2021, at 5:22 PM, Tom Seewald <tseewald@gmail.com> wrote:
>
> Hi,
>
> Has this been abandoned or will there be future attempts at syncing the
> in-kernel zstd with the upstream project?
>
> Tom
Sorry for the lack of action, but this has not been abandoned. I’ve just been
preparing a rebased patch-set last week, so expect to see some action soon.
Since we’re not in a merge window, I’m unsure if it is best to send out the
updated patches now, or wait until the merge window is open, but I’m about to
pose that question to the LKML.
This work has been on my back burner, because I’ve been busy with work on
Zstd and other projects, and have had a hard time justifying to myself spending
too much time on this, since progress has been so slow.
Best,
Nick Terrell
next prev parent reply other threads:[~2021-09-29 1:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 0:22 [GIT PULL][PATCH v11 0/4] Update to zstd-1.4.10 Tom Seewald
2021-09-29 0:55 ` Neal Gompa
2021-09-29 1:30 ` Nick Terrell [this message]
2021-09-29 10:06 ` David Sterba
2021-09-29 10:23 ` Paul Jones
2021-09-29 16:56 ` Nick Terrell
2021-09-29 20:02 ` Oleksandr Natalenko
-- strict thread matches above, loose matches on Subject: below --
2021-04-30 1:31 Nick Terrell
2021-05-11 20:53 ` Nick Terrell
2021-05-12 19:49 ` David Sterba
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=4A374EA5-F4CC-4C41-A810-90D09CB7A5FB@fb.com \
--to=terrelln@fb.com \
--cc=B093B859-53CC-4818-8CC3-A317F4872AD6@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).