From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] add PROP_TYPE_ENUM and print_options callback
Date: Tue, 25 Jan 2011 17:58:19 +0200 [thread overview]
Message-ID: <20110125155819.GA21640@playa.tlv.redhat.com> (raw)
In-Reply-To: <1295348320-32099-1-git-send-email-alevy@redhat.com>
On Tue, Jan 18, 2011 at 12:58:37PM +0200, Alon Levy wrote:
> This patchset allows a new property type called PROP_TYPE_ENUM,
> I want to use it for the backend property in the ccid patches (will
> send the patchset that uses it after this), libvirt is the ultimate
> user.
Ping.
Anthony - this is required for the ccid patch I will sent (ok, a little
predictive) since it makes choosing a backend for ccid-card-emulated simpler,
all the string comparing is here.
Looking at other devices this can be used:
* ivshmem.c: role
>
> The first patch adds a print_options callback that works with this
> property type to print the optional values.
>
> The second patch allows storing the name/value mapping in the property,
> using a void ptr for later different uses.
>
> The third patch adds the property itself.
>
> Alon Levy (3):
> qdev: add print_options callback
> qdev: add data pointer to Property
> qdev-properties: add PROP_TYPE_ENUM
>
> hw/qdev-properties.c | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/qdev.c | 10 +++++++-
> hw/qdev.h | 17 ++++++++++++++
> 3 files changed, 86 insertions(+), 1 deletions(-)
>
> --
> 1.7.3.4
>
>
prev parent reply other threads:[~2011-01-25 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 10:58 [Qemu-devel] [PATCH 0/3] add PROP_TYPE_ENUM and print_options callback Alon Levy
2011-01-18 10:58 ` [Qemu-devel] [PATCH 1/3] qdev: add " Alon Levy
2011-01-18 10:58 ` [Qemu-devel] [PATCH 2/3] qdev: add data pointer to Property Alon Levy
2011-01-18 10:58 ` [Qemu-devel] [PATCH 3/3] qdev-properties: add PROP_TYPE_ENUM Alon Levy
2011-01-25 15:58 ` Alon Levy [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=20110125155819.GA21640@playa.tlv.redhat.com \
--to=alevy@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.