From: Thiemo Seufer <ths@networkno.de>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-ppc: add integer Altivec instructions
Date: Sun, 14 Dec 2008 17:19:50 +0100 [thread overview]
Message-ID: <20081214161950.GB7738@networkno.de> (raw)
In-Reply-To: <20081213190849.GA23471@codesourcery.com>
Nathan Froyd wrote:
> This patch series adds support for integer Altivec instructions to QEMU,
> including element-wise loads and stores. It's rather long (42
> individual patches), so to avoid patch-bombing the list, I've placed the
> patch series at:
>
> http://www.method-combination.net/qemu/altivec-patches/
Please patch-bomb instead, so we have patch and related discussion
(and signed-off lines) in the same mail archive.
Thiemo
prev parent reply other threads:[~2008-12-14 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 19:08 [Qemu-devel] [PATCH] target-ppc: add integer Altivec instructions Nathan Froyd
[not found] ` <5C882EC3-989B-4ED0-9EE7-BAB88161037A@hotmail.com>
2008-12-13 23:37 ` C.W. Betts
2008-12-13 23:45 ` Nathan Froyd
2008-12-14 16:19 ` Thiemo Seufer [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=20081214161950.GB7738@networkno.de \
--to=ths@networkno.de \
--cc=froydnj@codesourcery.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).