Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libffi: bump to version 3.3-rc0
Date: Fri, 9 Nov 2018 22:20:59 +0100	[thread overview]
Message-ID: <20181109222059.02b14ea5@windsurf> (raw)
In-Reply-To: <20181109180004.29604-1-fontaine.fabrice@gmail.com>

Hello,

On Fri,  9 Nov 2018 19:00:04 +0100, Fabrice Fontaine wrote:
> - Update site to github (for the time being, as 3.3-rc0 is a release
>   candidate, it is not published on the official ftp)
> - Update third patch
> - Remove fourth and fifth patches (already in version)
> - Remove uneeded hooks, as public headers are now installed in the
>   standard path since
>   https://github.com/libffi/libffi/commit/982b89c01aca99c7bc229914fc1521f96930919b
> - New risc-v support:
>   https://github.com/libffi/libffi/commit/3840d49aaa831d649b1597518a2903dfed0d57f3
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/3edf66362ea5a83291f19373e4b6f2e5cce98d7b
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...-hardfloat-in-the-MIPS-assembly-code.patch |  5 +-
>  ...004-m68k-support-ISA-A-Coldfire-CPUs.patch | 77 -------------------
>  ...005-mips-use-__linux__-and-not-linux.patch | 37 ---------
>  package/libffi/libffi.hash                    |  4 +-
>  package/libffi/libffi.mk                      | 26 +------
>  5 files changed, 8 insertions(+), 141 deletions(-)
>  delete mode 100644 package/libffi/0004-m68k-support-ISA-A-Coldfire-CPUs.patch
>  delete mode 100644 package/libffi/0005-mips-use-__linux__-and-not-linux.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-11-09 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 18:00 [Buildroot] [PATCH 1/1] libffi: bump to version 3.3-rc0 Fabrice Fontaine
2018-11-09 21:20 ` Thomas Petazzoni [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=20181109222059.02b14ea5@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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