From: "Kővágó Zoltán" <dirty.ice.hu@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH v2] qapi for audio backends
Date: Fri, 05 Jun 2015 15:54:35 +0200 [thread overview]
Message-ID: <5571AA1B.8060800@gmail.com> (raw)
In-Reply-To: <1433501871.4142.9.camel@redhat.com>
Hi,
2015-06-05 12:57 keltezéssel, Gerd Hoffmann írta:
>> Yeah, I've already hit a problem. The opts_visitor doesn't really handle
>> nested structs (it just flattens it into a single, non hierarchic
>> namespace), which is a problem because of the input and output options.
>> First I need to make them required (the in and out in Audiodev) if I
>> want the current visitor to visit them at all, but it's still not enough.
>
> I think we should improve the visitor instead of making in & out
> mandatory just because the current implementation (which simply
> implements the stuff needed for Netdev) can't handle it.
It's not that simple I think. The visit_optional only receives a field
name, but no info about the type of the field, but it has to decide if
it wants the field using only this info. So sort of hacking an if
(strcmp(name, "in") == 0 || strcmp(name, "out") == 0) ... into the
option visitor code, the only way is probably to add a type parameter to
visit_optional (struct/union/uint32/whatever) and in the opts visitor if
type is struct or union, force visiting it. Is it ok?
> There is always the option to be more specific (in.frequency=...) if
> setting all parameters named 'frequency' doesn't do what you want. Also
> I wouldn't worry too much about possible cases which don't exist right
> now. I'd suggest to go for (0).
Alright.
Thanks,
Zoltan
next prev parent reply other threads:[~2015-06-05 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 13:39 [Qemu-devel] [RFC PATCH v2] qapi for audio backends Kővágó, Zoltán
2015-06-04 15:30 ` Gerd Hoffmann
2015-06-04 22:08 ` Kővágó Zoltán
2015-06-05 10:57 ` Gerd Hoffmann
2015-06-05 13:54 ` Kővágó Zoltán [this message]
2015-06-08 7:42 ` Gerd Hoffmann
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=5571AA1B.8060800@gmail.com \
--to=dirty.ice.hu@gmail.com \
--cc=kraxel@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).