From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-devel@nongnu.org,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Thomas Huth <thuth@redhat.com>, Wei Xu <wexu@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] virtio-net: Fix VirtIONet typedef redefinition
Date: Tue, 22 Jan 2019 00:04:27 -0500 [thread overview]
Message-ID: <20190122000421-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190121181030.2112-1-philmd@redhat.com>
On Mon, Jan 21, 2019 at 07:10:30PM +0100, Philippe Mathieu-Daudé wrote:
> Commit 2974e916df8 introduced the VirtioNetRscChain structure which
> refer to a VirtIONet, declared later, thus required VirtIONet typedef
> to be declarated forward.
> However, when compiling with Clang in -std=gnu99 mode, this triggers
> the following warning/error:
>
> CC hw/net/virtio-net.o
> In file included from qemu/hw/net/virtio-net.c:22:
> include/hw/virtio/virtio-net.h:189:3: error: redefinition of typedef 'VirtIONet' is a C11 feature [-Werror,-Wtypedef-redefinition]
> } VirtIONet;
> ^
> include/hw/virtio/virtio-net.h:110:26: note: previous definition is here
> typedef struct VirtIONet VirtIONet;
> ^
> 1 error generated.
> make: *** [rules.mak:69: hw/net/virtio-net.o] Error 1
>
> Fix it by removing the duplicate typedef definition.
>
> Reported-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> include/hw/virtio/virtio-net.h | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/include/hw/virtio/virtio-net.h b/include/hw/virtio/virtio-net.h
> index c7ec1a755f..bd662752d2 100644
> --- a/include/hw/virtio/virtio-net.h
> +++ b/include/hw/virtio/virtio-net.h
> @@ -106,7 +106,6 @@ typedef struct VirtioNetRscSeg {
> NetClientState *nc;
> } VirtioNetRscSeg;
>
> -struct VirtIONet;
> typedef struct VirtIONet VirtIONet;
>
> /* Chain is divided by protocol(ipv4/v6) and NetClientInfo */
> @@ -136,7 +135,7 @@ typedef struct VirtIONetQueue {
> struct VirtIONet *n;
> } VirtIONetQueue;
>
> -typedef struct VirtIONet {
> +struct VirtIONet {
> VirtIODevice parent_obj;
> uint8_t mac[ETH_ALEN];
> uint16_t status;
> @@ -186,7 +185,7 @@ typedef struct VirtIONet {
> int announce_counter;
> bool needs_vnet_hdr_swap;
> bool mtu_bypass_backend;
> -} VirtIONet;
> +};
>
> void virtio_net_set_netclient_name(VirtIONet *n, const char *name,
> const char *type);
> --
> 2.20.1
prev parent reply other threads:[~2019-01-22 5:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 18:10 [Qemu-devel] [PATCH] virtio-net: Fix VirtIONet typedef redefinition Philippe Mathieu-Daudé
2019-01-21 19:22 ` Eric Blake
2019-01-21 19:46 ` Philippe Mathieu-Daudé
2019-01-22 4:28 ` Thomas Huth
2019-01-22 5:05 ` Michael S. Tsirkin
2019-01-22 5:23 ` Thomas Huth
2019-01-22 13:55 ` Michael S. Tsirkin
2019-01-21 21:53 ` Greg Kurz
2019-01-22 5:04 ` 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=20190122000421-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wexu@redhat.com \
--cc=yuri.benditovich@daynix.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 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).