From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] zstd: Version bump 1.5.2 -> 1.5.4
Date: Fri, 17 Feb 2023 16:35:22 +0100 [thread overview]
Message-ID: <20230217153522.1204977-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230210133123.2702654-1-christian.melki@t2data.com>
Thanks, applied as 64917b5111c444e6f6deaca5c6863e37eda94bd7.
Michael
[sent from post-receive hook]
On Fri, 17 Feb 2023 16:35:22 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> A "big", minor version bump.
> https://github.com/facebook/zstd/releases/tag/v1.5.4
> Actually so big they skipped 1.5.3?
>
> Even though it's > 650 commits, From a normal end user
> perspective it's mostly performance improvments and
> some improvements to dictionary compression and large file handling.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230210133123.2702654-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/zstd.make b/rules/zstd.make
> index 7198117c3720..fee30fa8c171 100644
> --- a/rules/zstd.make
> +++ b/rules/zstd.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_ZSTD) += zstd
> #
> # Paths and names
> #
> -ZSTD_VERSION := 1.5.2
> -ZSTD_MD5 := 6dc24b78e32e7c99f80c9441e40ff8bc
> +ZSTD_VERSION := 1.5.4
> +ZSTD_MD5 := 02b49acde4ebb35f7e47a2a41032ffa8
> ZSTD := zstd-$(ZSTD_VERSION)
> ZSTD_SUFFIX := tar.gz
> ZSTD_URL := https://github.com/facebook/zstd/archive/v$(ZSTD_VERSION).$(ZSTD_SUFFIX)
prev parent reply other threads:[~2023-02-17 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 13:31 [ptxdist] [PATCH] " Christian Melki
2023-02-17 15:35 ` Michael Olbrich [this message]
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=20230217153522.1204977-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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