From: Paolo Bonzini <pbonzini@redhat.com>
To: "Doug Goldstein" <cardoe@gentoo.org>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Aurélien Jarno" <aurelien@aurel32.net>
Cc: James Hogan <james.hogan@imgtec.com>,
Mike Frysinger <vapier@gentoo.org>,
qemu-devel <qemu-devel@nongnu.org>,
qemu-stable@nongnu.org, Stefan Weil <stefan.weil@weilnetz.de>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] configure: detect endian via compile test
Date: Thu, 26 Sep 2013 22:54:08 +0200 [thread overview]
Message-ID: <52449EF0.3090406@redhat.com> (raw)
In-Reply-To: <CAFWqQMRDEpm6ZFry8zLAW4tpsEihgrnESVGha4FtZvnWAE_rJw@mail.gmail.com>
Il 26/09/2013 05:22, Doug Goldstein ha scritto:
> On Mon, Sep 9, 2013 at 2:30 PM, Stefan Weil <stefan.weil@weilnetz.de> wrote:
>> Am 28.08.2013 10:21, schrieb James Hogan:
>>> On 1 July 2013 04:30, Mike Frysinger <vapier@gentoo.org> wrote:
>>>> This avoids needing to execute a program and keeping an (incomplete)
>>>> list when cross-compiling. Signed-off-by: Mike Frysinger
>>>> <vapier@gentoo.org>
>>> This fixes mipsel cross compiling. I also checked it detected a mips
>>> (be) compiler as big endian. Tested-by: James Hogan
>>> <james.hogan@imgtec.com> [mips] Can somebody please apply this. Maybe
>>> for stable too? Cheers James
>>
>> Ping? Aurelien, Anthony, who wants to commit this patch?
>> Richard already reviewed it.
>>
>> See also http://patchwork.ozlabs.org/patch/268687/ for
>> another configure patch waiting for a commit.
>>
>> Regards,
>> Stefan
>>
>>
>
> Ping on getting this into master (and then over to stable).
>
Thanks Doug. Anthony, Aurelien, can you commit it?
Paolo
next prev parent reply other threads:[~2013-09-26 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 3:30 [Qemu-devel] [PATCH] configure: detect endian via compile test Mike Frysinger
2013-07-02 15:19 ` Richard Henderson
2013-08-28 8:21 ` James Hogan
2013-09-09 19:30 ` Stefan Weil
2013-09-26 3:22 ` Doug Goldstein
2013-09-26 20:54 ` Paolo Bonzini [this message]
2013-11-05 17:36 ` Peter Maydell
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=52449EF0.3090406@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=cardoe@gentoo.org \
--cc=james.hogan@imgtec.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefan.weil@weilnetz.de \
--cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.