From: Jeff Cody <jcody@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] block/vhdx.c: Mark parent_vhdx_guid variable as unused
Date: Mon, 15 Sep 2014 08:08:53 -0400 [thread overview]
Message-ID: <20140915120853.GA18505@localhost.localdomain> (raw)
In-Reply-To: <1410722999-17574-1-git-send-email-peter.maydell@linaro.org>
On Sun, Sep 14, 2014 at 08:29:59PM +0100, Peter Maydell wrote:
> The parent_vhdx_guid variable is defined but never used, which provokes
> complaints from newer versions of clang. Since the variable definition
> is here acting as documentation of the image format, mark it with the
> 'unused' attribute to keep the compiler happy rather than simply
> deleting it.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> block/vhdx.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/block/vhdx.c b/block/vhdx.c
> index 87c99fc..367a3e7 100644
> --- a/block/vhdx.c
> +++ b/block/vhdx.c
> @@ -99,7 +99,8 @@ static const MSGUID logical_sector_guid = { .data1 = 0x8141bf1d,
> /* Each parent type must have a valid GUID; this is for parent images
> * of type 'VHDX'. If we were to allow e.g. a QCOW2 parent, we would
> * need to make up our own QCOW2 GUID type */
> -static const MSGUID parent_vhdx_guid = { .data1 = 0xb04aefb7,
> +static const MSGUID parent_vhdx_guid __attribute__((unused))
> + = { .data1 = 0xb04aefb7,
> .data2 = 0xd19e,
> .data3 = 0x4a81,
> .data4 = { 0xb7, 0x89, 0x25, 0xb8,
> --
> 2.0.0
>
Reviewed-by: Jeff Cody <jcody@redhat.com>
next prev parent reply other threads:[~2014-09-15 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 19:29 [Qemu-devel] [PATCH] block/vhdx.c: Mark parent_vhdx_guid variable as unused Peter Maydell
2014-09-15 1:39 ` Fam Zheng
2014-09-15 12:08 ` Jeff Cody [this message]
2014-09-15 15:45 ` Stefan Hajnoczi
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=20140915120853.GA18505@localhost.localdomain \
--to=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).