qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas_ml@monjalon.net>
To: qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] Re: [PATCH v2 0/5] fix & clean PPC e300
Date: Tue, 27 Apr 2010 23:18:31 +0200	[thread overview]
Message-ID: <201004272318.32014.thomas_ml@monjalon.net> (raw)
In-Reply-To: <m2hf43fc5581004271147hd72f9e42n194e7d78987f07f4@mail.gmail.com>

Blue Swirl wrote:
> On 4/27/10, Thomas Monjalon <thomas_ml@monjalon.net> wrote:
> >  The only improvement is in the fix for RFI/RFID.
> >  Please Blue Swirl, could you test with Altivec ?
> 
> Sorry, I don't have one.

Oops, sorry. I have "CCed" the author of the commit 2ada0ed. But it was the 
SVN old time. I should look at the Signed-off line.

Alexander, you have made the commit 2ada0ed to fix Altivec. Could you check 
that the 4th patch of this serie doesn't break Altivec ?
Thanks
-- 
Thomas

      reply	other threads:[~2010-04-27 21:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 15:31 [Qemu-devel] [PATCH v2 0/5] fix & clean PPC e300 Thomas Monjalon
2010-04-27 15:31 ` [Qemu-devel] [PATCH v2 1/5] target-ppc: fix processor versions (PVR) for e300 Thomas Monjalon
2010-04-27 15:31 ` [Qemu-devel] [PATCH v2 2/5] target-ppc: fix interrupt vectors for MPC603 and e300 Thomas Monjalon
2010-04-27 15:31 ` [Qemu-devel] [PATCH v2 3/5] target-ppc: exception model of 603e inherits from 603 Thomas Monjalon
2010-04-27 15:31 ` [Qemu-devel] [PATCH v2 4/5] target-ppc: fix RFI by clearing upper bytes of MSR Thomas Monjalon
2010-05-02  8:12   ` Alexander Graf
2010-05-18 14:00     ` Thomas Monjalon
2010-05-18 14:35       ` Alexander Graf
2010-05-18 15:17         ` Thomas Monjalon
2010-04-27 15:31 ` [Qemu-devel] [PATCH v2 5/5] ppc: remove dead code Thomas Monjalon
2010-04-27 18:47 ` [Qemu-devel] Re: [PATCH v2 0/5] fix & clean PPC e300 Blue Swirl
2010-04-27 21:18   ` Thomas Monjalon [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=201004272318.32014.thomas_ml@monjalon.net \
    --to=thomas_ml@monjalon.net \
    --cc=agraf@suse.de \
    --cc=blauwirbel@gmail.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).