From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Linnea Gunnarsson <linnea.gunnarsson@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libseccomp: version bump 2.5.3 -> 2.5.4
Date: Mon, 9 May 2022 08:28:53 +0200 [thread overview]
Message-ID: <20220509062853.3753993-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220425133947.2361036-1-linnea.gunnarsson@t2data.com>
Thanks, applied as 69e33a118e1105f1c0dfed10e446154fa4e47f98.
Michael
[sent from post-receive hook]
On Mon, 09 May 2022 08:28:53 +0200, Linnea Gunnarsson <linnea.gunnarsson@t2data.com> wrote:
> - Updated syscall table for Linux 5.17.
> - Minor fixes with binary trees.
> - Minor documentation improvements.
>
> Patch applied successfully.
>
> Signed-off-by: Linnea Gunnarsson <linnea.gunnarsson@t2data.com>
> Message-Id: <20220425133947.2361036-1-linnea.gunnarsson@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libseccomp-2.5.3/0001-run-time-use-a-broadly-supported-shell-interpreter.patch b/patches/libseccomp-2.5.4/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> similarity index 100%
> rename from patches/libseccomp-2.5.3/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> rename to patches/libseccomp-2.5.4/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> diff --git a/patches/libseccomp-2.5.3/series b/patches/libseccomp-2.5.4/series
> similarity index 100%
> rename from patches/libseccomp-2.5.3/series
> rename to patches/libseccomp-2.5.4/series
> diff --git a/rules/libseccomp.make b/rules/libseccomp.make
> index 5a6f45f1ccb2..b3b99c189627 100644
> --- a/rules/libseccomp.make
> +++ b/rules/libseccomp.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBSECCOMP) += libseccomp
> #
> # Paths and names
> #
> -LIBSECCOMP_VERSION := 2.5.3
> -LIBSECCOMP_MD5 := 5096d3912a605a72b27805fa0ef9886d
> +LIBSECCOMP_VERSION := 2.5.4
> +LIBSECCOMP_MD5 := 74008bb33234e0c2a0d998e7bee5c625
> 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:[~2022-05-09 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 13:39 [ptxdist] [PATCH] " Linnea Gunnarsson
2022-05-09 6:28 ` 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=20220509062853.3753993-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=linnea.gunnarsson@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