From: Blue Swirl <blauwirbel@gmail.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] Small monitor cleanup
Date: Wed, 10 Jun 2009 19:59:20 +0300 [thread overview]
Message-ID: <f43fc5580906100959w33443107l1a3b94e09f2c3354@mail.gmail.com> (raw)
In-Reply-To: <1244584070.7164.20.camel@blaa>
On 6/10/09, Mark McLoughlin <markmc@redhat.com> wrote:
> On Tue, 2009-06-09 at 18:20 -0300, Luiz Capitulino wrote:
> > Hi there,
> >
> > This patch series contains simple patches to simplify monitor's
> > monitor_handle_command() function a bit.
>
>
> They all look like sensible and safe cleanups to me.
>
> Reviewed-by: Mark McLoughlin <markmc@redhat.com>
Thanks, applied all.
prev parent reply other threads:[~2009-06-10 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 21:20 [Qemu-devel] [PATCH 0/4] Small monitor cleanup Luiz Capitulino
2009-06-09 21:47 ` Mark McLoughlin
2009-06-10 16:59 ` 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=f43fc5580906100959w33443107l1a3b94e09f2c3354@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=markmc@redhat.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).