From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Johan Hovold <johan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: io_edgeport: mark expected switch fall-throughs
Date: Mon, 2 Jul 2018 08:00:43 -0500 [thread overview]
Message-ID: <3a1b5c84-091d-7f7d-2fcf-206ccd4f91af@embeddedor.com> (raw)
In-Reply-To: <20180702085100.GF9802@localhost>
Hi Johan,
On 07/02/2018 03:51 AM, Johan Hovold wrote:
> On Thu, Jun 28, 2018 at 01:40:30PM -0500, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
>> where we are expecting to fall through.
>>
>> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
>> ---
>> drivers/usb/serial/io_edgeport.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/serial/io_edgeport.c b/drivers/usb/serial/io_edgeport.c
>> index 97c69d3..441dab6 100644
>> --- a/drivers/usb/serial/io_edgeport.c
>> +++ b/drivers/usb/serial/io_edgeport.c
>> @@ -1760,7 +1760,7 @@ static void process_rcvd_data(struct edgeport_serial *edge_serial,
>> edge_serial->rxState = EXPECT_HDR2;
>> break;
>> }
>> - /* otherwise, drop on through */
>> + /* else: fall through */
>
> This doesn't silence the compiler warning with gcc 7.2.0 as the "else: "
> pattern isn't recognised.
>
I'm using level 2:
-Wimplicit-fallthrough=2
The thing here is that some people have pointed out that it can be misleading to
place a plain fall-through comment after an if-else code block containing a "break".
So, the solution above has proved to be a good one.
>> case EXPECT_HDR2:
>> edge_serial->rxHeader2 = *buffer;
>> ++buffer;
>> @@ -1820,7 +1820,7 @@ static void process_rcvd_data(struct edgeport_serial *edge_serial,
>> edge_serial->rxState = EXPECT_DATA;
>> break;
>> }
>> - /* Else, drop through */
>> + /* else: fall through */
>> }
>
> And this doesn't work either due to the "else: " as well as the fact
> that the compiler expects the fallthrough comment to precede the case
> statement directly (e.g. it would need to be moved out of the else
> block, but that isn't necessarily desirable as we discussed last year:
>
> lkml.kernel.org/r/20171027203906.GA7054@embeddedor.com
>
Yes. I'm aware of that. This certainly is still triggering a warning, so I just consider this
as a temporal approach. I still need to define how are we going to manage cases like this.
> )
>
>> case EXPECT_DATA: /* Expect data */
>> if (bufferLength < edge_serial->rxBytesRemaining) {
>
> How do you compile test these these patches?
>
I already explained this above.
Thanks for your comments.
--
Gustavo
next prev parent reply other threads:[~2018-07-02 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 18:40 Gustavo A. R. Silva
2018-07-02 8:51 ` Johan Hovold
2018-07-02 13:00 ` Gustavo A. R. Silva [this message]
2018-07-02 15:16 ` Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2017-10-27 20:39 Gustavo A. R. Silva
2017-10-28 10:56 ` Bjørn Mork
2017-10-28 23:47 ` Gustavo A. R. Silva
2017-10-30 11:54 ` David Laight
2017-10-30 14:42 ` Johan Hovold
2017-10-31 4:50 ` Gustavo A. R. Silva
2017-10-31 7:49 ` Johan Hovold
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=3a1b5c84-091d-7f7d-2fcf-206ccd4f91af@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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
all inboxes | Powered by JetHome®