From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Darren Hart <dvhart@infradead.org>
Cc: "Matthew Garrett" <mjg59@srcf.ucam.org>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Andy Shevchenko" <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: dell-laptop: Mark expected switch fall-throughs
Date: Tue, 19 Feb 2019 10:33:53 -0600 [thread overview]
Message-ID: <4d97e602-6de8-4b4f-86a8-39a835c1c699@embeddedor.com> (raw)
In-Reply-To: <20181129001533.GA2468@fedora.eng.vmware.com>
On 11/28/18 6:15 PM, Darren Hart wrote:
> On Thu, Jul 05, 2018 at 03:38:07PM -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>
>
> I've applied this patch, but not the acer or sony fall through patches
> due to the pending questions there. Happy to revisit those as needed,
> but closing these out of the patch queue.
>
Thanks, Darren.
I'll send separate patches for those that are still pending. Hopefully,
I'll get some feedback this time.
--
Gustavo
>> ---
>> drivers/platform/x86/dell-laptop.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/platform/x86/dell-laptop.c b/drivers/platform/x86/dell-laptop.c
>> index f1fa861..1938f11 100644
>> --- a/drivers/platform/x86/dell-laptop.c
>> +++ b/drivers/platform/x86/dell-laptop.c
>> @@ -1565,8 +1565,10 @@ static ssize_t kbd_led_timeout_store(struct device *dev,
>> switch (unit) {
>> case KBD_TIMEOUT_DAYS:
>> value *= 24;
>> + /* fall through */
>> case KBD_TIMEOUT_HOURS:
>> value *= 60;
>> + /* fall through */
>> case KBD_TIMEOUT_MINUTES:
>> value *= 60;
>> unit = KBD_TIMEOUT_SECONDS;
>> --
>> 2.7.4
>>
>>
>
prev parent reply other threads:[~2019-02-19 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 20:38 Gustavo A. R. Silva
2018-11-29 0:15 ` Darren Hart
2019-02-19 16:33 ` 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=4d97e602-6de8-4b4f-86a8-39a835c1c699@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@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®