From: Darren Hart <dvhart@infradead.org>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: Mattia Dongili <malattia@linux.it>,
Andy Shevchenko <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: sony-laptop: Mark expected switch fall-through
Date: Fri, 6 Jul 2018 16:24:27 -0700 [thread overview]
Message-ID: <20180706232427.GC3041@fury> (raw)
In-Reply-To: <20180705204703.GA12352@embeddedor.com>
On Thu, Jul 05, 2018 at 03:47:03PM -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/platform/x86/sony-laptop.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/platform/x86/sony-laptop.c b/drivers/platform/x86/sony-laptop.c
> index b205b03..e614cb7 100644
> --- a/drivers/platform/x86/sony-laptop.c
> +++ b/drivers/platform/x86/sony-laptop.c
> @@ -4427,6 +4427,7 @@ sony_pic_read_possible_resource(struct acpi_resource *resource, void *context)
> default:
> dprintk("Resource %d isn't an IRQ nor an IO port\n",
> resource->type);
> + /* fall through */
Here too, I wonder if this is intentional. Either way, from what I can see, the
final line in the function:
return AE_CTRL_TERMINATE;
Is unreachable as there are no "break" statements in the switch, and the default
falls through to return AE_OK. Something doesn't seem right here.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-07-06 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 20:47 [PATCH] platform/x86: sony-laptop: Mark expected switch fall-through Gustavo A. R. Silva
2018-07-06 23:24 ` Darren Hart [this message]
2018-07-07 16:19 ` Andy Shevchenko
2018-07-07 18:56 ` Mattia Dongili
2018-09-11 22:51 ` Darren Hart
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=20180706232427.GC3041@fury \
--to=dvhart@infradead.org \
--cc=andy@infradead.org \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malattia@linux.it \
--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