From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Anthony Green <green@moxielogic.com>
Cc: Andrew Haley <aph@redhat.com>,
"libffi-discuss\@sourceware.org"
<libffi-discuss@sourceware.org>,
gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: Unreviewed libffi patch
Date: Wed, 22 May 2013 11:49:00 -0000 [thread overview]
Message-ID: <yddzjvns084.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CACxje59X_rLcSd7NO1yUNQEjRjeN9hoNkv+FSbA4MNiKxa9FpQ@mail.gmail.com> (Anthony Green's message of "Wed, 22 May 2013 07:17:00 -0400")
Anthony Green <green@moxielogic.com> writes:
> Rainer - sorry, I've been travelling and falling behind on email.
> This patch is fine. Please commit it to GCC. I'll put it in the
> libffi git tree.
No worries, I just saw your vacation note. I've commited to mainline
now.
Jakub, what should we do about the 4.8 branch? Wait until 4.8.1 is
released or apply now? This is a regression from 4.7.
Thanks.
Rainer
> On Wed, May 22, 2013 at 5:58 AM, Andrew Haley <aph@redhat.com> wrote:
>
> On 05/22/2013 10:55 AM, Rainer Orth wrote:
> > The following libffi patch
> >
> > [libffi] Fix several libffi testsuite failures on 64-bit
> SPARC and PowerPC (PR libffi/56033)
> > http://gcc.gnu.org/ml/gcc-patches/2013-05/msg00840.html
> >
> > has remained unreviewed for a week. It needs a libffi
> maintainer, which
> > I suppose Anthony still is, despite not being listed in
> MAINTAINERS.
>
> Forwarding to libffi.
>
>
>
>
>
>
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2013-05-22 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yddk3mrtk3k.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
2013-05-22 9:58 ` Andrew Haley
[not found] ` <CACxje59X_rLcSd7NO1yUNQEjRjeN9hoNkv+FSbA4MNiKxa9FpQ@mail.gmail.com>
2013-05-22 11:49 ` Rainer Orth [this message]
2013-05-22 12:40 ` Jakub Jelinek
2013-05-22 12:45 ` Rainer Orth
[not found] <yddpqmg5tgk.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
2011-06-14 15:38 ` Andrew Haley
2011-06-14 16:02 ` Rainer Orth
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=yddzjvns084.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=green@moxielogic.com \
--cc=jakub@redhat.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).