From: Eric Blake <eblake@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vnc: Add break statement
Date: Sat, 25 Feb 2012 07:18:11 -0700 [thread overview]
Message-ID: <4F48EDA3.2080700@redhat.com> (raw)
In-Reply-To: <1330178223-31717-1-git-send-email-sw@weilnetz.de>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On 02/25/2012 06:57 AM, Stefan Weil wrote:
> This was not a bug, but it is not common practice to omit the break statement
> from the last case statement before an empty default case.
>
> Any change of the default case would introduce a bug.
>
> This was reported as a warning by splint.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> ui/vnc-enc-hextile-template.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/ui/vnc-enc-hextile-template.h b/ui/vnc-enc-hextile-template.h
> index b9f9f5e..a7310e1 100644
> --- a/ui/vnc-enc-hextile-template.h
> +++ b/ui/vnc-enc-hextile-template.h
> @@ -175,6 +175,7 @@ static void CONCAT(send_hextile_tile_, NAME)(VncState *vs,
> /* we really don't have to invalidate either the bg or fg
> but we've lost the old values. oh well. */
> }
> + break;
TABs vs. space looks odd. Does this file also need a whitespace cleanup?
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2012-02-25 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 13:57 [Qemu-devel] [PATCH] vnc: Add break statement Stefan Weil
2012-02-25 14:18 ` Eric Blake [this message]
2012-02-25 14:38 ` Stefan Weil
2012-02-25 15:57 ` Andreas Färber
2012-02-25 16:09 ` Stefan Weil
2012-02-25 16:18 ` Andreas Färber
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=4F48EDA3.2080700@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/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).