From: Richard Henderson <rth@twiddle.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 0/6] AREG0 patches v5
Date: Mon, 13 Feb 2012 15:41:49 -0800 [thread overview]
Message-ID: <4F399FBD.4050302@twiddle.net> (raw)
In-Reply-To: <CAAu8pHt77bce+ONpdFvcZCiVf0mrT9Twy=NogqHLrU4xnoCvaQ@mail.gmail.com>
On 02/13/2012 12:13 PM, Blue Swirl wrote:
> Blue Swirl (6):
> TCG: split i386 and x86_64
> TCG: clean up i386 and x86_64
I object to these. I do NOT think splitting these makes the code base
as a whole any cleaner.
Is this really just about the differences wrt the softmmu templates?
Surely that can be handled without duping the entire host port...
r~
next prev parent reply other threads:[~2012-02-13 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 20:13 [Qemu-devel] [PATCH 0/6] AREG0 patches v5 Blue Swirl
2012-02-13 23:41 ` Richard Henderson [this message]
2012-02-14 11:38 ` Andreas Färber
2012-02-14 17:01 ` Richard Henderson
2012-02-14 18:54 ` Blue Swirl
2012-02-14 19:39 ` Richard Henderson
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=4F399FBD.4050302@twiddle.net \
--to=rth@twiddle.net \
--cc=aurelien@aurel32.net \
--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).