From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] zlib: Version bump. 1.3.1 -> 1.3.2
Date: Mon, 2 Mar 2026 10:25:23 +0100 [thread overview]
Message-ID: <20260302092523.3502520-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260221190612.2881087-1-christian.melki@t2data.com>
Thanks, applied as af7c9ed1fe933f631dd615a660706d5fd5e6c731.
Michael
[sent from post-receive hook]
On Mon, 02 Mar 2026 10:25:23 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Some time in the making. Probably plugs a bunch of holes.
> https://github.com/madler/zlib/blob/v1.3.2/ChangeLog
> https://github.com/madler/zlib/blob/v1.3.1.2/ChangeLog
>
> * Copyright year changed.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260221190612.2881087-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/zlib.make b/rules/zlib.make
> index 50cc89520e4f..95320db9593d 100644
> --- a/rules/zlib.make
> +++ b/rules/zlib.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_ZLIB) += zlib
> # Paths and names
> #
>
> -ZLIB_VERSION := 1.3.1
> -ZLIB_MD5 := 5e6af153311327e516690d300527ec9e
> +ZLIB_VERSION := 1.3.2
> +ZLIB_MD5 := be8a129ec5d60c5084911fd7ea16d84e
> ZLIB := zlib-$(ZLIB_VERSION)
> ZLIB_SUFFIX := tar.xz
> ZLIB_URL := \
> @@ -27,7 +27,7 @@ ZLIB_SOURCE := $(SRCDIR)/$(ZLIB).$(ZLIB_SUFFIX)
> ZLIB_DIR := $(BUILDDIR)/$(ZLIB)
> ZLIB_LICENSE := Zlib
> ZLIB_LICENSE_FILES := \
> - file://LICENSE;md5=b51a40671bc46e961c0498897742c0b8
> + file://LICENSE;md5=66e4e749bb11d80fc7ba510a9ce99534
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2026-03-02 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 19:06 [ptxdist] [PATCH] " Christian Melki
2026-03-02 9:25 ` 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=20260302092523.3502520-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