From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, John Arbuckle <programmingkidx@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] hw/audio/sb16.c: missing break statement
Date: Thu, 8 Feb 2018 13:08:49 +0000 [thread overview]
Message-ID: <20180208130849.GC20703@redhat.com> (raw)
In-Reply-To: <caaad0dd-3f8e-a414-48ed-b6535d5a83a4@amsat.org>
On Thu, Feb 08, 2018 at 09:15:10AM -0300, Philippe Mathieu-Daudé wrote:
> Hi Daniel,
>
> On 02/08/2018 07:57 AM, Daniel Henrique Barboza wrote:
> > This patch adds a break in the switch() statement of complete(),
> > value 0x42:
> >
> > case 0x42: /* FT2 sets output freq with this, go figure */
> > qemu_log_mask(LOG_UNIMP, "cmd 0x42 might not do what it think it"
> > " should\n");
> > break; <-------
> > case 0x41:
>
> It seems this is an intentional fallthrough, I understand cmd 0x42 is
> expected to do the same of 0x41 and _a bit more_ (see commit 85571bc7415).
It might be nice to turn on -Wimplicit-fallthrough and then annotate
valid locations like this in qemu with /* fallthrough */
Although GCC has an __attribute((fallthrough)), the warning flag impl
also looks for that magic comment, and the magic comment is portable
to clang too.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-02-08 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 10:57 [Qemu-devel] [PATCH 1/1] hw/audio/sb16.c: missing break statement Daniel Henrique Barboza
2018-02-08 12:15 ` Philippe Mathieu-Daudé
2018-02-08 13:01 ` Peter Maydell
2018-02-08 13:16 ` Philippe Mathieu-Daudé
2018-02-08 13:34 ` Philippe Mathieu-Daudé
2018-02-08 13:51 ` Peter Maydell
2018-02-08 13:08 ` Daniel P. Berrangé [this message]
2018-02-08 14:11 ` Daniel Henrique Barboza
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=20180208130849.GC20703@redhat.com \
--to=berrange@redhat.com \
--cc=danielhb@linux.vnet.ibm.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=programmingkidx@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).