From: Tom Musta <tommusta@gmail.com>
To: Richard Henderson <rth@twiddle.net>, qemu-devel@nongnu.org
Cc: ulrich.weigand@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2 00/26] Merge ppc32/ppc64 tcg backends
Date: Thu, 19 Jun 2014 07:46:04 -0500 [thread overview]
Message-ID: <53A2DB8C.1050804@gmail.com> (raw)
In-Reply-To: <538506CA.9050109@gmail.com>
On 5/27/2014 4:42 PM, Tom Musta wrote:
> On 5/27/2014 4:26 PM, Richard Henderson wrote:
>> Please review, and if you've got an ELFv2 system (nudge nudge), please
>> give it a try and make sure it works.
>
> Tested-by: Tom Musta <tommusta@gmail.com>
>
Will this series get into 2.1? The ELFv2 support is of particular interest.
next parent reply other threads:[~2014-06-19 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1401225995-31230-1-git-send-email-rth@twiddle.net>
[not found] ` <538506CA.9050109@gmail.com>
2014-06-19 12:46 ` Tom Musta [this message]
2014-06-19 20:04 ` [Qemu-devel] [PATCH v2 00/26] Merge ppc32/ppc64 tcg backends 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=53A2DB8C.1050804@gmail.com \
--to=tommusta@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=ulrich.weigand@de.ibm.com \
/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 NNTP newsgroup(s).