From: David Howells <dhowells@redhat.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, Kees Cook <keescook@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] afs: Mark expected switch fall-throughs
Date: Tue, 09 Apr 2019 10:34:52 +0100 [thread overview]
Message-ID: <2695.1554802492@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190110220245.GA20942@embeddedor>
Gustavo A. R. Silva <gustavo@embeddedor.com> wrote:
Please fix the compiler so that you can annotate a switch-statement to say
that every case must fall through (except, perhaps, the last).
> /* extract the FID array and its count in two steps */
> + /* fall through */
> case 1:
Capitialise "Fall" for consistency, please, and can you put the fall-through
marker *before* the comment introducing the case please? It belongs to the
preceding section.
> /* extract the callback array and its count in two steps */
> + /* fall through */
> case 3:
Ditto.
> /* extract the FID array and its count in two steps */
> + /* Fall through */
Ditto on putting the fall-through before the introductory comment.
(And more dittos).
> - /* Extract fsEndpoints[] entries */
> + /* Fall through - and extract fsEndpoints[] entries */
And here you're doing something different yet again, though you could drop
either the "-" or the "and".
David
next prev parent reply other threads:[~2019-04-09 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 22:02 [PATCH] afs: Mark expected switch fall-throughs Gustavo A. R. Silva
2019-04-09 0:10 ` Kees Cook
2019-04-09 9:28 ` David Howells
2019-04-09 15:18 ` Kees Cook
2019-04-16 13:35 ` David Howells
2019-04-09 9:34 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-17 11:36 Gustavo A. R. Silva
2018-07-31 21:58 Gustavo A. R. Silva
2018-08-02 9:12 ` David Howells
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=2695.1554802492@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=gustavo@embeddedor.com \
--cc=keescook@google.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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