From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 00/11] GCC 4.6.0 fixes
Date: Thu, 07 Oct 2010 09:29:25 +0200 [thread overview]
Message-ID: <4CAD76D5.3050901@redhat.com> (raw)
In-Reply-To: <AANLkTikHKfP_DGM3EeG505EJQEn76HSi4=qKF5ibx4Z4@mail.gmail.com>
On 10/06/2010 11:31 PM, Blue Swirl wrote:
> Blue Swirl (11):
> block: avoid a write only variable
> cirrus: avoid write only variables
> eepro100: initialize a variable in all cases
> lsi53c895a: avoid a write only variable
> Delete write only variables
> mips_fulong2e: Delete write only variables
> cris: avoid write only variables
> vnc: avoid write only variables
> i386: avoid a write only variable
> ppc: avoid write only variables
> mips: avoid write only variables
>
> block/qcow2-refcount.c | 18 +-
> hw/cirrus_vga.c | 30 +-
> hw/cirrus_vga_rop.h | 38 +-
> hw/cirrus_vga_rop2.h | 12 +-
> hw/eepro100.c | 6 +-
> hw/lsi53c895a.c | 7 +-
> hw/mips_fulong2e.c | 8 +-
> hw/mips_malta.c | 14 +-
> hw/mips_r4k.c | 3 +-
> hw/ppc405_boards.c | 5 +-
> hw/ppc405_uc.c | 28 -
> hw/ppc_newworld.c | 3 +-
> hw/ppc_oldworld.c | 6 +-
> hw/ppc_prep.c | 3 +-
> hw/ppce500_mpc8544ds.c | 13 +-
> hw/tc6393xb_template.h | 2 -
> hw/virtex_ml507.c | 5 +-
> hw/wm8750.c | 5 -
> net/tap-win32.c | 5 +-
> savevm.c | 4 +-
> target-cris/op_helper.c | 6 +
> target-cris/translate_v10.c | 5 +-
> target-i386/op_helper.c | 4 +-
> target-mips/translate.c | 1222 +++++++++++++++++++++++--------------------
> target-ppc/op_helper.c | 20 +-
> ui/vnc.c | 8 +
> 26 files changed, 769 insertions(+), 711 deletions(-)
I replied to the patches I disagree with. Otherwise a nice cleanup.
Paolo
prev parent reply other threads:[~2010-10-07 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 21:31 [Qemu-devel] [PATCH 00/11] GCC 4.6.0 fixes Blue Swirl
2010-10-07 7:29 ` Paolo Bonzini [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=4CAD76D5.3050901@redhat.com \
--to=pbonzini@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 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.