From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, armbru@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qapi: Drop dead genlist parameter
Date: Fri, 10 Apr 2015 15:04:08 -0600 [thread overview]
Message-ID: <55283AC8.9090109@redhat.com> (raw)
In-Reply-To: <1428699583-15237-1-git-send-email-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
On 04/10/2015 02:59 PM, Eric Blake wrote:
> Defaulting a parameter to True, then having all callers omit
> or pass an explicit True for that parameter, is pointless.
> Looks like it has been dead since introduction in commit 06d64c6.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> scripts/qapi-visit.py | 36 ++++++++++++++++--------------------
> 1 file changed, 16 insertions(+), 20 deletions(-)
> @@ -510,8 +507,7 @@ exprs = parse_schema(input_file)
> # for built-in types in our header files and simply guard them
> fdecl.write(guardstart("QAPI_VISIT_BUILTIN_VISITOR_DECL"))
> for typename in builtin_types.keys():
Sorry; this doesn't apply to current master. I'll send a v2 that
doesn't depend on my pending qapi nested struct series.
> - fdecl.write(generate_declaration(typename, None, genlist=True,
> - builtin_type=True))
> + fdecl.write(generate_declaration(typename, None, builtin_type=True))
> fdecl.write(guardend("QAPI_VISIT_BUILTIN_VISITOR_DECL"))
>
> # ...this doesn't work for cases where we link in multiple objects that
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-04-10 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 20:59 [Qemu-devel] [PATCH] qapi: Drop dead genlist parameter Eric Blake
2015-04-10 21:04 ` Eric Blake [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=55283AC8.9090109@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).