From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] libseccomp: add license file and hash
Date: Tue, 28 Nov 2023 09:36:43 +0100 [thread overview]
Message-ID: <20231128083643.1039061-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231119200819.38425-6-bruno.thomsen@gmail.com>
Thanks, applied as d9ea9bceac0bcede4e9171ddf35d27054986eb53.
Michael
[sent from post-receive hook]
On Tue, 28 Nov 2023 09:36:43 +0100, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20231119200819.38425-6-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libseccomp.make b/rules/libseccomp.make
> index b3b99c189627..b7ad65dfa5cb 100644
> --- a/rules/libseccomp.make
> +++ b/rules/libseccomp.make
> @@ -14,14 +14,16 @@ PACKAGES-$(PTXCONF_LIBSECCOMP) += libseccomp
> #
> # Paths and names
> #
> -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)
> -LIBSECCOMP_SOURCE := $(SRCDIR)/$(LIBSECCOMP).$(LIBSECCOMP_SUFFIX)
> -LIBSECCOMP_DIR := $(BUILDDIR)/$(LIBSECCOMP)
> -LIBSECCOMP_LICENSE := LGPL-2.1-only
> +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)
> +LIBSECCOMP_SOURCE := $(SRCDIR)/$(LIBSECCOMP).$(LIBSECCOMP_SUFFIX)
> +LIBSECCOMP_DIR := $(BUILDDIR)/$(LIBSECCOMP)
> +LIBSECCOMP_LICENSE := LGPL-2.1-only
> +LIBSECCOMP_LICENSE_FILES := \
> + file://LICENSE;md5=7c13b3376cea0ce68d2d2da0a1b3a72c
>
> # ----------------------------------------------------------------------------
> # Prepare
next prev parent reply other threads:[~2023-11-28 8:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 20:08 [ptxdist] [PATCH 1/8] libestr: " Bruno Thomsen
2023-11-19 20:08 ` [ptxdist] [PATCH 2/8] libffi: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 3/8] libmbim: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 4/8] libndp: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 5/8] libp11: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 6/8] libseccomp: " Bruno Thomsen
2023-11-28 8:36 ` Michael Olbrich [this message]
2023-11-19 20:08 ` [ptxdist] [PATCH 7/8] p11-kit: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 8/8] python3-ply: update license Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] libestr: add license file and hash Michael Olbrich
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=20231128083643.1039061-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bruno.thomsen@gmail.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