From: Laurent Vivier <Laurent@Vivier.EU>
To: "Guo, Lei" <guol-fnst@cn.fujitsu.com>,
"Andreas Färber" <afaerber@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Thomas Huth <thuth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] 答复: Add CMP2 instruction
Date: Mon, 10 Nov 2014 12:30:44 +0100 [thread overview]
Message-ID: <5460A1E4.6060406@Vivier.EU> (raw)
In-Reply-To: <36D1AB4E1AAC4541A1C88167C7231D0B74C307@G08CNEXMBPEKD02.g08.fujitsu.local>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Le 10/11/2014 04:21, Guo, Lei a écrit :
> Hi Andreas
> Thanks a lot for your patients. Because I'm a newer to this , I'll follow your advices and pay much more attention to these details.
> Besides ,I have replied to Thomas' question on my previous submission.
If the question was "Have you been in touch with the author of that
original patch already?", I can affirm the answer is "no".
It's opensoure, grab what you want, but if you resend a patch you must
let the "Signed-off-by".
BTW, "CMP2" is neither generated by gcc or used by linux, why do you
want to add it to an old and obsolete architecture ? Do you have a "real
life" test case for it ?
If you send a correct and tested new patch, I can add it in my tree.
Mainline QEMU doesn't care of m68k (680x0) support.
For those who want to know why I don't submit my patches the reasons are :
- they break coldfire support
- there is a bug in MMU emulation that prevent linux to fork new
processes (I'm hunting this for 2 years now...)
Regards,
Laurent
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-11-10 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 10:14 [Qemu-devel] Add CMP2 instruction Guo, Lei
2014-11-07 11:10 ` Alex Bennée
2014-11-07 11:15 ` Andreas Färber
2014-11-10 3:21 ` [Qemu-devel] 答复: " Guo, Lei
2014-11-10 11:30 ` Laurent Vivier [this message]
2014-11-07 11:26 ` [Qemu-devel] " Richard Henderson
2014-11-07 11:57 ` Laurent Vivier
2014-11-07 13:44 ` Laurent Vivier
2014-11-07 20:05 ` Andreas Schwab
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=5460A1E4.6060406@Vivier.EU \
--to=laurent@vivier.eu \
--cc=afaerber@suse.de \
--cc=guol-fnst@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=schwab@linux-m68k.org \
--cc=thuth@linux.vnet.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 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.