From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 01/11] block: avoid a write only variable
Date: Thu, 07 Oct 2010 13:55:46 +0200 [thread overview]
Message-ID: <4CADB542.6040803@redhat.com> (raw)
In-Reply-To: <m3y6aapcn5.fsf@blackfin.pond.sub.org>
Am 07.10.2010 11:37, schrieb Markus Armbruster:
> Blue Swirl <blauwirbel@gmail.com> writes:
>
>> Compiling with GCC 4.6.0 20100925 produced a warning:
>> /src/qemu/block/qcow2-refcount.c: In function 'update_refcount':
>> /src/qemu/block/qcow2-refcount.c:552:13: error: variable 'dummy' set
>> but not used [-Werror=unused-but-set-variable]
>>
>> Fix by adding a function that does not generate a warning when
>> the result is unused.
>
> What about a simple "(void)dummy" instead?
I would prefer that, too.
Kevin
next prev parent reply other threads:[~2010-10-07 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 21:31 [Qemu-devel] [PATCH 01/11] block: avoid a write only variable Blue Swirl
2010-10-07 9:37 ` Markus Armbruster
2010-10-07 11:55 ` Kevin Wolf [this message]
2010-10-07 18:27 ` Blue Swirl
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=4CADB542.6040803@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@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).