From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libseccomp: Version bump. 2.5.4 -> 2.5.5
Date: Thu, 7 Dec 2023 12:10:01 +0100 [thread overview]
Message-ID: <20231207111001.1329153-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231203214151.978083-1-christian.melki@t2data.com>
Thanks, applied as 07132f64af3d54491070c188c547fb9d0b905872.
Michael
[sent from post-receive hook]
On Thu, 07 Dec 2023 12:10:01 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Very minor syscall table update.
>
> * Forward patchset, applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20231203214151.978083-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libseccomp-2.5.4/0001-run-time-use-a-broadly-supported-shell-interpreter.patch b/patches/libseccomp-2.5.5/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> similarity index 100%
> rename from patches/libseccomp-2.5.4/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> rename to patches/libseccomp-2.5.5/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> diff --git a/patches/libseccomp-2.5.4/series b/patches/libseccomp-2.5.5/series
> similarity index 100%
> rename from patches/libseccomp-2.5.4/series
> rename to patches/libseccomp-2.5.5/series
> diff --git a/rules/libseccomp.make b/rules/libseccomp.make
> index b7ad65dfa5cb..48fbf8f7fc50 100644
> --- a/rules/libseccomp.make
> +++ b/rules/libseccomp.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBSECCOMP) += libseccomp
> #
> # Paths and names
> #
> -LIBSECCOMP_VERSION := 2.5.4
> -LIBSECCOMP_MD5 := 74008bb33234e0c2a0d998e7bee5c625
> +LIBSECCOMP_VERSION := 2.5.5
> +LIBSECCOMP_MD5 := c27a5e43cae1e89e6ebfedeea734c9b4
> LIBSECCOMP := libseccomp-$(LIBSECCOMP_VERSION)
> LIBSECCOMP_SUFFIX := tar.gz
> LIBSECCOMP_URL := https://github.com/seccomp/libseccomp/releases/download/v$(LIBSECCOMP_VERSION)/$(LIBSECCOMP).$(LIBSECCOMP_SUFFIX)
prev parent reply other threads:[~2023-12-07 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 21:41 [ptxdist] [PATCH] " Christian Melki
2023-12-07 11:10 ` 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=20231207111001.1329153-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