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.7.1 -> 3.8.0
Date: Fri, 4 Sep 2026 08:52:58 +0200 [thread overview]
Message-ID: <20260904065258.10671-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260817203830.981947-1-christian.melki@t2data.com>
Thanks, applied as 9391024e7cd0bd894bb5337433deafdb2065a094.
Michael
[sent from post-receive hook]
On Fri, 04 Sep 2026 08:52:58 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> https://github.com/libffi/libffi/releases/tag/v3.8.0
>
> * Forward patchset, applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260817203830.981947-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/libffi-3.7.1/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch b/patches/libffi-3.8.0/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> similarity index 100%
> rename from patches/libffi-3.7.1/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> rename to patches/libffi-3.8.0/0001-libffi-Fix-location-of-libraries-for-multilib-toolch.patch
> diff --git a/patches/libffi-3.7.1/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch b/patches/libffi-3.8.0/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> similarity index 100%
> rename from patches/libffi-3.7.1/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> rename to patches/libffi-3.8.0/0002-libffi-ensure-sysroot-paths-are-not-in-libffi.pc.patch
> diff --git a/patches/libffi-3.7.1/autogen.sh b/patches/libffi-3.8.0/autogen.sh
> similarity index 100%
> rename from patches/libffi-3.7.1/autogen.sh
> rename to patches/libffi-3.8.0/autogen.sh
> diff --git a/patches/libffi-3.7.1/series b/patches/libffi-3.8.0/series
> similarity index 100%
> rename from patches/libffi-3.7.1/series
> rename to patches/libffi-3.8.0/series
> diff --git a/rules/libffi.make b/rules/libffi.make
> index 0404c3a6d95e..9b42feb348e9 100644
> --- a/rules/libffi.make
> +++ b/rules/libffi.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBFFI) += libffi
> #
> # Paths and names
> #
> -LIBFFI_VERSION := 3.7.1
> -LIBFFI_SHA256 := d5e9a6638ddbd2513ddb54518eb67e4bbe6fa707bcc01c10f6212f0a088d819d
> +LIBFFI_VERSION := 3.8.0
> +LIBFFI_SHA256 := 7da3e2d9a171eb0a038f592ecad3ff2bb2550f3496d87b3b29ad0cf4430c0db4
> LIBFFI := libffi-$(LIBFFI_VERSION)
> LIBFFI_SUFFIX := tar.gz
> LIBFFI_SOURCE := $(SRCDIR)/$(LIBFFI).$(LIBFFI_SUFFIX)
prev parent reply other threads:[~2026-09-04 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 20:38 [ptxdist] [PATCH] " Christian Melki
2026-09-04 6:52 ` 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=20260904065258.10671-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