From: Markus Armbruster <armbru@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Kashyap Chamarthy <kchamart@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qapi/misc.json: Remove superfluous words in CpuModelExpansionType
Date: Tue, 09 Oct 2018 13:47:30 +0200 [thread overview]
Message-ID: <87sh1fxrxp.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20181003190057.GG5738@habkost.net> (Eduardo Habkost's message of "Wed, 3 Oct 2018 16:00:57 -0300")
Eduardo Habkost <ehabkost@redhat.com> writes:
> On Wed, Oct 03, 2018 at 12:46:05PM +0200, Kashyap Chamarthy wrote:
>> While at it, s/QMU/QEMU in @CpuDefinitionInfo.
>>
>> Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
>
> Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
>
> Will this go through the QAPI tree?
Queued with the commit message updated as requested by Kashyap. Thanks!
prev parent reply other threads:[~2018-10-09 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 10:46 [Qemu-devel] [PATCH] qapi/misc.json: Remove superfluous words in CpuModelExpansionType Kashyap Chamarthy
2018-10-03 11:11 ` Marc-André Lureau
2018-10-03 14:26 ` Eric Blake
2018-10-04 9:24 ` Kashyap Chamarthy
2018-10-03 19:00 ` Eduardo Habkost
2018-10-09 11:47 ` Markus Armbruster [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=87sh1fxrxp.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kchamart@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 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.