From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 00/13] coding style nits
Date: Wed, 30 Sep 2009 19:43:23 +0200 [thread overview]
Message-ID: <20090930174323.GA1399@redhat.com> (raw)
Running gnu indent on qemu mangles the code horribly, but also produced
some useful warnings. Here are some fixes.
--
MST
Michael S. Tsirkin (13):
vvfat: fix coding style nit
elfload: fix coding style nit
gdbstub: fix coding style nit
escc: fix coding style nit
omap_dma: fix unbalanced { in commented out code
twl92230: fix old style increment/decrement usage
linux-user: fix old style decrement usage
target-mips: unmatched brackets in if 0
tests: unmatched brackets in if 0
linux-user: fix coding style nit
net: fix coding style nit
slirp: fix unmatched bracket in if 0
escc: fix another coding style nit
block/vvfat.c | 4 ++--
bsd-user/elfload.c | 2 +-
gdbstub.c | 2 +-
hw/escc.c | 8 ++++----
hw/omap_dma.c | 4 +++-
hw/twl92230.c | 4 ++--
linux-user/arm/nwfpe/fpa11.c | 2 +-
linux-user/elfload.c | 2 +-
linux-user/syscall.c | 2 +-
net.c | 2 +-
slirp/ip_input.c | 2 --
target-mips/helper.c | 1 -
tests/sha1.c | 2 +-
13 files changed, 18 insertions(+), 19 deletions(-)
reply other threads:[~2009-09-30 17:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090930174323.GA1399@redhat.com \
--to=mst@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.