All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 09/10] chardev: Drop useless ChardevDummy type
Date: Fri, 4 Mar 2016 08:25:21 -0700	[thread overview]
Message-ID: <56D9A8E1.20105@redhat.com> (raw)
In-Reply-To: <8737s6xq5j.fsf@blackfin.pond.sub.org>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

On 03/04/2016 07:40 AM, Markus Armbruster wrote:
> Eric Blake <eblake@redhat.com> writes:
> 
>> Commit d0d7708b made ChardevDummy be an empty wrapper type around
>> ChardevCommon.  But there is no technical reason for this indirection,
>> so simplify the code by directly using the base type.
>>
>> Also change the fallback assignment to assign u.null rather than
>> u.data, since a future patch will remove the data member of the C
>> struct generated for QAPI unions.
>>
>> Signed-off-by: Eric Blake <eblake@redhat.com>
>> Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
> 
> Doesn't compile with MinGW:
> 
> qemu/qemu-char.c: In function 'qemu_chr_open_win_con':
> qemu/qemu-char.c:2186:29: warning: implicit declaration of function 'qapi_ChardevDummy_base' [-Wimplicit-function-declaration]
>      ChardevCommon *common = qapi_ChardevDummy_base(backend->u.console);
>                              ^

The curse of not compiling all the backends, and failing to grep for
ChardevDummy.  Replacement patch coming up soon.

-- 
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 --]

  reply	other threads:[~2016-03-04 15:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 16:16 [Qemu-devel] [PATCH v3 00/10] easier unboxed visits/qapi implicit types Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 01/10] qapi: Rename 'fields' to 'members' in generator Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 02/10] qapi: Rename 'fields' to 'members' in generated C code Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 03/10] qapi-visit: Expose visit_type_FOO_members() Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 04/10] qapi: Update docs to match recent generator changes Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 05/10] chardev: Shorten references into ChardevBackend Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 06/10] util: Shorten references into SocketAddress Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 07/10] ui: Shorten references into InputEvent Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 08/10] qapi: Avoid use of 'data' member of QAPI unions Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 09/10] chardev: Drop useless ChardevDummy type Eric Blake
2016-03-04 14:40   ` Markus Armbruster
2016-03-04 15:25     ` Eric Blake [this message]
2016-03-04 15:42   ` [Qemu-devel] [PATCH v3.5 " Eric Blake
2016-03-03 16:16 ` [Qemu-devel] [PATCH v3 10/10] qapi: Drop useless 'data' member of unions Eric Blake
2016-03-04 16:44 ` [Qemu-devel] [PATCH v3 00/10] easier unboxed visits/qapi implicit types Markus Armbruster

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=56D9A8E1.20105@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.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.