From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Roman Kagan" <rkagan@virtuozzo.com>,
qemu-devel@nongnu.org, "Igor Mammedov" <imammedo@redhat.com>,
"Ben Warren" <ben@skyportsystems.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
minyard@acm.org, "Denis V. Lunev" <den@openvz.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] add UUID property type
Date: Wed, 20 Dec 2017 16:13:40 +0200 [thread overview]
Message-ID: <20171220161328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20171220135130.GA6408@rkaganb.sw.ru>
On Wed, Dec 20, 2017 at 04:51:31PM +0300, Roman Kagan wrote:
> On Mon, Nov 27, 2017 at 04:05:16PM +0300, Roman Kagan wrote:
> > UUIDs (GUIDs) are widely used in VMBus-related stuff, so a dedicated
> > property type becomes helpful.
> >
> > In the existing code, vmgenid can immediately profit from it.
> >
> > Roman Kagan (2):
> > qdev-properties: add UUID property type
> > vmgenid: use UUID property type
> >
> > v1 -> v2:
> > - make the property default to autogeneration if not specified
> > explicitly
> > - use the corresponding define for "guid" field name
> >
> > include/hw/qdev-properties.h | 9 +++++++
> > hw/acpi/vmgenid.c | 30 ++++++----------------
> > hw/core/qdev-properties.c | 61 ++++++++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 78 insertions(+), 22 deletions(-)
>
> Ping?
It's in my queue, will be in the next pull request.
prev parent reply other threads:[~2017-12-20 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 13:05 [Qemu-devel] [PATCH v2 0/2] add UUID property type Roman Kagan
2017-11-27 13:05 ` [Qemu-devel] [PATCH v2 1/2] qdev-properties: " Roman Kagan
2017-11-27 16:53 ` Marc-André Lureau
2017-11-27 13:05 ` [Qemu-devel] [PATCH v2 2/2] vmgenid: use " Roman Kagan
2017-11-27 16:38 ` Ben Warren
2017-11-28 8:02 ` Roman Kagan
2017-11-28 14:46 ` Michael S. Tsirkin
2017-11-27 16:52 ` Marc-André Lureau
2017-12-20 13:51 ` [Qemu-devel] [PATCH v2 0/2] add " Roman Kagan
2017-12-20 14:13 ` Michael S. Tsirkin [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=20171220161328-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=ben@skyportsystems.com \
--cc=den@openvz.org \
--cc=imammedo@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=minyard@acm.org \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.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 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.