From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Andreas Helmcke <ahelmcke@ela-soft.com>
Subject: Re: [ptxdist] [APPLIED] haveged: version bump 1.9.18 -> 1.9.19
Date: Mon, 27 Apr 2026 09:46:06 +0200 [thread overview]
Message-ID: <20260427074606.52360-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260418182311.11653-5-ahelmcke@ela-soft.com>
Thanks, applied as 20e9bc5d15b6617b06e8129f7c96e8ea8ff9cf4f.
Michael
[sent from post-receive hook]
On Mon, 27 Apr 2026 09:46:06 +0200, Andreas Helmcke <ahelmcke@ela-soft.com> wrote:
> - Some bug fixes and improvements.
>
> link: https://github.com/jirka-h/haveged/releases/tag/v1.9.19
>
> - Copyright year update in license file.
>
> Signed-off-by: Andreas Helmcke <ahelmcke@ela-soft.com>
> Message-Id: <20260418182311.11653-5-ahelmcke@ela-soft.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/haveged.make b/rules/haveged.make
> index 85099e6d435b..17945799dc91 100644
> --- a/rules/haveged.make
> +++ b/rules/haveged.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_HAVEGED) += haveged
> #
> # Paths and names
> #
> -HAVEGED_VERSION := 1.9.18
> -HAVEGED_MD5 := 654ed186b6e2ec04d049b3edf4743187
> +HAVEGED_VERSION := 1.9.19
> +HAVEGED_MD5 := 715898625bd45062f1c8697f9aff2fe9
> HAVEGED := haveged-$(HAVEGED_VERSION)
> HAVEGED_SUFFIX := tar.gz
> HAVEGED_URL := \
> @@ -25,7 +25,7 @@ HAVEGED_DIR := $(BUILDDIR)/$(HAVEGED)
> HAVEGED_LICENSE := GPL-3.0-or-later
> HAVEGED_LICENSE_FILES := \
> file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
> - file://src/haveged.c;startline=1;endline=20;md5=f825c43c9190a988f49b137884675529
> + file://src/haveged.c;startline=1;endline=20;md5=4d0277c50e7cdae7b14dc63ae1766eea
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2026-04-27 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 18:23 [ptxdist] [PATCH] " Andreas Helmcke
2026-04-27 7:46 ` 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=20260427074606.52360-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ahelmcke@ela-soft.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