From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 00/11] Introduce host, emulator, machine and CPU states
Date: Fri, 15 Apr 2011 23:22:16 +0300 [thread overview]
Message-ID: <BANLkTi=EnH-Zkg7nGFX+uzsV=5k71H5Dxg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimq3E1ycgLfTxhjtQuWPCAW10PQgQ@mail.gmail.com>
On Fri, Apr 8, 2011 at 11:43 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
> The overall plan is to gather some functions and structures around
> "states" representing host, emulator, machine and (later) CPU. I see
> qemu-common.h as a library of useful stuff, it also includes
> OS-dependent declarations.
>
> Patches 1 to 7 are trivial. For 8 to 10, more review would be nice.
I applied patches 1 to 7. I'm still not 100% happy with the rest of
the patches, but maybe I'll apply in a few days if I don't come up
with something smarter.
prev parent reply other threads:[~2011-04-15 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 20:43 [Qemu-devel] [PATCH 00/11] Introduce host, emulator, machine and CPU states Blue Swirl
2011-04-15 20:22 ` Blue Swirl [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='BANLkTi=EnH-Zkg7nGFX+uzsV=5k71H5Dxg@mail.gmail.com' \
--to=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).