From: Stefan Weil <sw@weilnetz.de>
To: SeokYeon Hwang <syeon.hwang@samsung.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] vdi: wrapped uuid_unparse() in #ifdef
Date: Fri, 31 Oct 2014 19:15:25 +0100 [thread overview]
Message-ID: <5453D1BD.10902@weilnetz.de> (raw)
In-Reply-To: <1414742525-18639-1-git-send-email-syeon.hwang@samsung.com>
Am 31.10.2014 um 09:02 schrieb SeokYeon Hwang:
> Wrapped uuid_unparse() in #ifdef to avoid "-Wunused-function" on clang 3.4 or later.
>
> Signed-off-by: SeokYeon Hwang <syeon.hwang@samsung.com>
> ---
> block/vdi.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/block/vdi.c b/block/vdi.c
> index 19701ee..e1d211c 100644
> --- a/block/vdi.c
> +++ b/block/vdi.c
> @@ -137,12 +137,14 @@ static inline int uuid_is_null(const uuid_t uu)
> return memcmp(uu, null_uuid, sizeof(uuid_t)) == 0;
> }
>
> +# if defined(CONFIG_VDI_DEBUG)
> static inline void uuid_unparse(const uuid_t uu, char *out)
> {
> snprintf(out, 37, UUID_FMT,
> uu[0], uu[1], uu[2], uu[3], uu[4], uu[5], uu[6], uu[7],
> uu[8], uu[9], uu[10], uu[11], uu[12], uu[13], uu[14], uu[15]);
> }
> +# endif
> #endif
>
> typedef struct {
This code is only used on build hosts without libuuid development header
files, so the warning can be avoided by installing that header files.
Nevertheless, I think it is fine for qemu-trivial.
Reviewed-by: Stefan Weil <sw@weilnetz.de>
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Weil <sw@weilnetz.de>
To: SeokYeon Hwang <syeon.hwang@samsung.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vdi: wrapped uuid_unparse() in #ifdef
Date: Fri, 31 Oct 2014 19:15:25 +0100 [thread overview]
Message-ID: <5453D1BD.10902@weilnetz.de> (raw)
In-Reply-To: <1414742525-18639-1-git-send-email-syeon.hwang@samsung.com>
Am 31.10.2014 um 09:02 schrieb SeokYeon Hwang:
> Wrapped uuid_unparse() in #ifdef to avoid "-Wunused-function" on clang 3.4 or later.
>
> Signed-off-by: SeokYeon Hwang <syeon.hwang@samsung.com>
> ---
> block/vdi.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/block/vdi.c b/block/vdi.c
> index 19701ee..e1d211c 100644
> --- a/block/vdi.c
> +++ b/block/vdi.c
> @@ -137,12 +137,14 @@ static inline int uuid_is_null(const uuid_t uu)
> return memcmp(uu, null_uuid, sizeof(uuid_t)) == 0;
> }
>
> +# if defined(CONFIG_VDI_DEBUG)
> static inline void uuid_unparse(const uuid_t uu, char *out)
> {
> snprintf(out, 37, UUID_FMT,
> uu[0], uu[1], uu[2], uu[3], uu[4], uu[5], uu[6], uu[7],
> uu[8], uu[9], uu[10], uu[11], uu[12], uu[13], uu[14], uu[15]);
> }
> +# endif
> #endif
>
> typedef struct {
This code is only used on build hosts without libuuid development header
files, so the warning can be avoided by installing that header files.
Nevertheless, I think it is fine for qemu-trivial.
Reviewed-by: Stefan Weil <sw@weilnetz.de>
next prev parent reply other threads:[~2014-10-31 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 8:02 [Qemu-devel] [PATCH] vdi: wrapped uuid_unparse() in #ifdef SeokYeon Hwang
2014-10-31 18:15 ` Stefan Weil [this message]
2014-10-31 18:15 ` Stefan Weil
2014-11-02 5:14 ` [Qemu-trivial] " Michael Tokarev
2014-11-02 5:14 ` Michael Tokarev
2014-11-03 16:13 ` [Qemu-trivial] " Paolo Bonzini
2014-11-03 16:13 ` [Qemu-devel] " Paolo Bonzini
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=5453D1BD.10902@weilnetz.de \
--to=sw@weilnetz.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=syeon.hwang@samsung.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 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.