From: Aurelien Jarno <aurelien@aurel32.net>
To: chen huacai <zltjiangshi@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v6 0/7] MIPS: Initial support for fulong (Loongson-2E based) mini pc
Date: Tue, 29 Jun 2010 23:16:03 +0200 [thread overview]
Message-ID: <20100629211603.GC3811@ohm.aurel32.net> (raw)
In-Reply-To: <AANLkTinjdR-puvy7NlHN81S0-8oWB6Qo0XwDBRVj45LL@mail.gmail.com>
On Tue, Jun 29, 2010 at 10:46:35AM +0800, chen huacai wrote:
> Changes from V5:
> Clean up old style save/restore code
>
Thanks, all applied. However as said in answer to one of the previous
version of this series, 64-bit kernels fail to work. It would be nice to
follow up with patches to fix that. Also it would be nice to introduce
Loongson specific instructions (I can help on that, I already have a
quick and dirty patch to add them).
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2010-06-29 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 2:46 [Qemu-devel] [PATCH v6 0/7] MIPS: Initial support for fulong (Loongson-2E based) mini pc chen huacai
2010-06-29 21:16 ` Aurelien Jarno [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=20100629211603.GC3811@ohm.aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=zltjiangshi@gmail.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).