From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Guenter Roeck <linux@roeck-us.net>,
Zwane Mwaikambo <zwanem@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] watchdog: sc1200: Mark expected switch fall-through
Date: Tue, 26 Feb 2019 11:47:19 -0600 [thread overview]
Message-ID: <db73921e-f6dc-de1b-0f9b-be8d92b796dd@embeddedor.com> (raw)
In-Reply-To: <92afc448-e0c1-eaa4-8728-45af328e5163@roeck-us.net>
On 2/18/19 10:08 AM, Guenter Roeck wrote:
> On 2/14/19 12:20 PM, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
>> This patch fixes the following warning:
>>
>> drivers/watchdog/sc1200wdt.c: In function ‘sc1200wdt_ioctl’:
>> drivers/watchdog/sc1200wdt.c:241:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
>> sc1200wdt_write_data(WDTO, timeout);
>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/watchdog/sc1200wdt.c:244:2: note: here
>> case WDIOC_GETTIMEOUT:
>> ^~~~
>>
>> Warning level 3 was used: -Wimplicit-fallthrough=3
>>
>> Notice that, in this particular case, the code comment is modified
>> in accordance with what GCC is expecting to find.
>>
>> This patch is part of the ongoing efforts to enable
>> -Wimplicit-fallthrough.
>>
>> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>
Thank you, Guenter.
Friendly ping:
Who can take this?
Thanks
--
Gustavo
>> ---
>> drivers/watchdog/sc1200wdt.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/watchdog/sc1200wdt.c b/drivers/watchdog/sc1200wdt.c
>> index 8e4e2fc13f87..e035a4d4b299 100644
>> --- a/drivers/watchdog/sc1200wdt.c
>> +++ b/drivers/watchdog/sc1200wdt.c
>> @@ -239,7 +239,7 @@ static long sc1200wdt_ioctl(struct file *file, unsigned int cmd,
>> return -EINVAL;
>> timeout = new_timeout;
>> sc1200wdt_write_data(WDTO, timeout);
>> - /* fall through and return the new timeout */
>> + /* fall through - and return the new timeout */
>> case WDIOC_GETTIMEOUT:
>> return put_user(timeout * 60, p);
>>
>
prev parent reply other threads:[~2019-02-26 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 20:20 Gustavo A. R. Silva
2019-02-18 16:08 ` Guenter Roeck
2019-02-26 17:47 ` Gustavo A. R. Silva [this message]
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=db73921e-f6dc-de1b-0f9b-be8d92b796dd@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
--cc=zwanem@gmail.com \
/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®