From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Laurent Desnogues <laurent.desnogues@gmail.com>
Subject: Re: [Qemu-devel] Re: [PATCH][ARM] Fix wrong destination register for smuad, smusd, smlad, smlsd
Date: Wed, 25 Jun 2008 18:27:31 +0100 [thread overview]
Message-ID: <200806251827.37618.paul@codesourcery.com> (raw)
In-Reply-To: <761ea48b0806251015t4088f674hcacbc256b7a6dc0f@mail.gmail.com>
> Anyway, are you interested in a patch that corrects enough of
> v6 instructions that FFmpeg for ARMv6 works? Would FFmpeg
> be considered as a good enough test?
I'm generally more interested in the description/explanation of the patches
themselves. Saying "FOO works" is nice, but not as nice as convincing me
that you understand both the code you're changing, the arm architecture, and
that the two agree :-)
Paul
next prev parent reply other threads:[~2008-06-25 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 9:40 [Qemu-devel] [PATCH][ARM] Fix wrong destination register for smuad, smusd, smlad, smlsd Laurent Desnogues
2008-06-25 15:25 ` [Qemu-devel] " Laurent Desnogues
2008-06-25 16:58 ` Paul Brook
2008-06-25 17:15 ` Laurent Desnogues
2008-06-25 17:27 ` Paul Brook [this message]
2008-06-25 19:00 ` Laurent Desnogues
2008-06-25 19:11 ` Vincent Palatin
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=200806251827.37618.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=laurent.desnogues@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).