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.6.0 -> 2.6.1
Date: Wed, 15 Jul 2026 12:01:56 +0200 [thread overview]
Message-ID: <20260715100156.1255606-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260708182808.741741-1-christian.melki@t2data.com>
Thanks, applied as 27f71bb7e7dca1b5815b96f7b61e5b9fadd424fc.
Michael
[sent from post-receive hook]
On Wed, 15 Jul 2026 12:01:56 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Security fixes.
> https://github.com/seccomp/libseccomp/releases/tag/v2.6.1
>
> * Forward patchset, applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260708182808.741741-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libseccomp-2.6.0/0001-run-time-use-a-broadly-supported-shell-interpreter.patch b/patches/libseccomp-2.6.1/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> similarity index 100%
> rename from patches/libseccomp-2.6.0/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> rename to patches/libseccomp-2.6.1/0001-run-time-use-a-broadly-supported-shell-interpreter.patch
> diff --git a/patches/libseccomp-2.6.0/series b/patches/libseccomp-2.6.1/series
> similarity index 100%
> rename from patches/libseccomp-2.6.0/series
> rename to patches/libseccomp-2.6.1/series
> diff --git a/rules/libseccomp.make b/rules/libseccomp.make
> index b4060412d4c9..ee65064c5c95 100644
> --- a/rules/libseccomp.make
> +++ b/rules/libseccomp.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBSECCOMP) += libseccomp
> #
> # Paths and names
> #
> -LIBSECCOMP_VERSION := 2.6.0
> -LIBSECCOMP_SHA256 := 83b6085232d1588c379dc9b9cae47bb37407cf262e6e74993c61ba72d2a784dc
> +LIBSECCOMP_VERSION := 2.6.1
> +LIBSECCOMP_SHA256 := 501f66c667225d53791b97e1d7cf85ab764c297d04881f60f38f451c4b0ee1be
> 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:[~2026-07-15 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 18:28 [ptxdist] [PATCH] " Christian Melki
2026-07-15 10:01 ` 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=20260715100156.1255606-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