From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] fix a few clang warnings
Date: Tue, 26 Jan 2010 20:09:09 -0600 [thread overview]
Message-ID: <4B5FA045.7090404@codemonkey.ws> (raw)
In-Reply-To: <1264547685-21129-1-git-send-email-pbonzini@redhat.com>
On 01/26/2010 05:14 PM, Paolo Bonzini wrote:
> All of these should be quite uncontroversial. The vnc.c change is
> not what you'd expect though (could be a real bug, so I leave the
> clang warning).
>
I'm scratching my head quite a bit on these. Can you resend the series
with commit messages that actually explain what the problem clang is
reporting and why it fixes it.
The vnc one is just whacky.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-01-27 2:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 23:14 [Qemu-devel] [PATCH 0/6] fix a few clang warnings Paolo Bonzini
2010-01-26 23:14 ` [Qemu-devel] [PATCH 1/6] remove two dead assignments in target-i386/translate.c Paolo Bonzini
2010-01-26 23:14 ` [Qemu-devel] [PATCH 2/6] fix undefined shifts by >32 Paolo Bonzini
2010-01-26 23:14 ` [Qemu-devel] [PATCH 3/6] exec.c: dead assignments Paolo Bonzini
2010-01-26 23:14 ` [Qemu-devel] [PATCH 4/6] vnc.c: warn about ignored option Paolo Bonzini
2010-01-27 2:10 ` Anthony Liguori
2010-01-27 10:00 ` Gerd Hoffmann
2010-01-26 23:14 ` [Qemu-devel] [PATCH 5/6] usb-linux.c: remove write-only variable Paolo Bonzini
2010-01-26 23:14 ` [Qemu-devel] [PATCH 6/6] fix audio_bug related failures Paolo Bonzini
2010-01-27 2:10 ` Anthony Liguori
2010-01-27 11:56 ` [Qemu-devel] " Paolo Bonzini
2010-01-27 21:43 ` Anthony Liguori
2010-01-31 3:08 ` malc
2010-01-31 10:21 ` Paolo Bonzini
2010-01-27 2:09 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 13:54 [Qemu-devel] [PATCH 0/6] fix a few clang warnings 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=4B5FA045.7090404@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=pbonzini@redhat.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).