From: Anthony Green <green@moxielogic.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: "libffi-discuss\@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: libffi 3.2 and disruptive changes
Date: Wed, 12 Nov 2014 12:04:00 -0000 [thread overview]
Message-ID: <87fvdotyjv.fsf@moxielogic.com> (raw)
In-Reply-To: <20141111145909.GA8500@arm.com> (James Greenhalgh's message of "Tue, 11 Nov 2014 14:59:09 +0000")
James Greenhalgh <james.greenhalgh@arm.com> writes:
> AArch64 linux builds are still broken (Alan Lawrence posted a patch at
> https://sourceware.org/ml/libffi-discuss/2014/msg00091.html )
>
> Could we please have that patch in for the 3.2 release?
I've just tagged and released 3.2.1 with this fix.
Thanks,
AG
next prev parent reply other threads:[~2014-11-12 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 14:53 Anthony Green
2014-11-11 14:59 ` James Greenhalgh
2014-11-12 12:04 ` Anthony Green [this message]
2014-11-11 15:01 ` Alan Lawrence
2014-11-12 7:16 ` Dominik Vogt
2014-11-12 7:22 ` Richard Henderson
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=87fvdotyjv.fsf@moxielogic.com \
--to=green@moxielogic.com \
--cc=james.greenhalgh@arm.com \
--cc=libffi-discuss@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).