From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libffi: Version bump. 3.4.6 -> 3.4.7
Date: Mon, 17 Feb 2025 08:24:37 +0100 [thread overview]
Message-ID: <20250217072437.52680-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250212193122.2681945-1-christian.melki@t2data.com>
Thanks, applied as 586b9f8f84cef82893d53b258760f0981af81631.
Michael
[sent from post-receive hook]
On Mon, 17 Feb 2025 08:24:37 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Mostly fixes.
> https://github.com/libffi/libffi/releases/tag/v3.4.7
>
> * Forward patches, applies cleanly
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250212193122.2681945-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libffi-3.4.6/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch b/patches/libffi-3.4.7/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> similarity index 100%
> rename from patches/libffi-3.4.6/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> rename to patches/libffi-3.4.7/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> diff --git a/patches/libffi-3.4.6/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch b/patches/libffi-3.4.7/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> similarity index 100%
> rename from patches/libffi-3.4.6/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> rename to patches/libffi-3.4.7/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> diff --git a/patches/libffi-3.4.6/autogen.sh b/patches/libffi-3.4.7/autogen.sh
> similarity index 100%
> rename from patches/libffi-3.4.6/autogen.sh
> rename to patches/libffi-3.4.7/autogen.sh
> diff --git a/patches/libffi-3.4.6/series b/patches/libffi-3.4.7/series
> similarity index 100%
> rename from patches/libffi-3.4.6/series
> rename to patches/libffi-3.4.7/series
> diff --git a/rules/libffi.make b/rules/libffi.make
> index f9a6bd397045..f983b1beaabe 100644
> --- a/rules/libffi.make
> +++ b/rules/libffi.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBFFI) += libffi
> #
> # Paths and names
> #
> -LIBFFI_VERSION := 3.4.6
> -LIBFFI_MD5 := b9cac6c5997dca2b3787a59ede34e0eb
> +LIBFFI_VERSION := 3.4.7
> +LIBFFI_MD5 := 696a1d483a1174ce8a477575546a5284
> LIBFFI := libffi-$(LIBFFI_VERSION)
> LIBFFI_SUFFIX := tar.gz
> LIBFFI_SOURCE := $(SRCDIR)/$(LIBFFI).$(LIBFFI_SUFFIX)
prev parent reply other threads:[~2025-02-17 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 19:31 [ptxdist] [PATCH] " Christian Melki
2025-02-17 7:24 ` 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=20250217072437.52680-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