From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] lz4: version bump 1.9.4 -> 1.10.0
Date: Fri, 17 Oct 2025 10:20:59 +0200 [thread overview]
Message-ID: <20251017082059.3112878-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251013105312.1598053-1-s.pueschel@pengutronix.de>
Thanks, applied as 7570af141e5281d7501498c16836a2be940ebef9.
Michael
[sent from post-receive hook]
On Fri, 17 Oct 2025 10:20:59 +0200, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> lz4 now has multithreading support for compression/decompression🎉:
> https://github.com/lz4/lz4/releases/tag/v1.10.0
>
> The old GitHub URL has changed, as the old repository was moved to a
> dedicated organization. GitHub automatically redirects to the new
> location.
>
> The licenses were updated to properly reflect GPL2.0-or-later instead
> of GPLv2-only, see
> https://github.com/lz4/lz4/commit/aafb56ee2ed40fb6b994f87af4e8560865df7c85
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20251013105312.1598053-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/lz4.make b/rules/lz4.make
> index 4b9b2bb33076..de88c1b7c943 100644
> --- a/rules/lz4.make
> +++ b/rules/lz4.make
> @@ -14,18 +14,18 @@ PACKAGES-$(PTXCONF_LZ4) += lz4
> #
> # Paths and names
> #
> -LZ4_VERSION := 1.9.4
> -LZ4_MD5 := e9286adb64040071c5e23498bf753261
> +LZ4_VERSION := 1.10.0
> +LZ4_MD5 := dead9f5f1966d9ae56e1e32761e4e675
> LZ4 := lz4-$(LZ4_VERSION)
> LZ4_SUFFIX := tar.gz
> -LZ4_URL := https://github.com/Cyan4973/lz4/archive/v$(LZ4_VERSION).$(LZ4_SUFFIX)
> +LZ4_URL := https://github.com/lz4/lz4/archive/v$(LZ4_VERSION).$(LZ4_SUFFIX)
> LZ4_SOURCE := $(SRCDIR)/$(LZ4).$(LZ4_SUFFIX)
> LZ4_DIR := $(BUILDDIR)/$(LZ4)
> LZ4_LICENSE := BSD-2-Clause AND GPL-2.0-or-later
> LZ4_LICENSE_FILES := \
> - file://LICENSE;md5=c5cc3cd6f9274b4d32988096df9c3ec3 \
> + file://LICENSE;md5=c111c47e301c2ffe8776729b40b44477 \
> file://lib/LICENSE;md5=5cd5f851b52ec832b10eedb3f01f885a \
> - file://programs/COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263
> + file://programs/COPYING;md5=492daf447d6db0e5eb344a7922e7ec25
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2025-10-17 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 10:52 [ptxdist] [PATCH] " Sven Püschel
2025-10-17 8:20 ` 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=20251017082059.3112878-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.pueschel@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