From: Quan Nguyen <quan@os.amperecomputing.com>
To: Guenter Roeck <linux@roeck-us.net>,
Nathan Chancellor <nathan@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, patches@lists.linux.dev
Subject: Re: [PATCH -next v2] hwmon: (smpro-hwmon) Improve switch statments in smpro_is_visible()
Date: Sat, 29 Oct 2022 15:49:24 +0700 [thread overview]
Message-ID: <0ea97349-afad-e0ab-09c7-f61c782555a0@os.amperecomputing.com> (raw)
In-Reply-To: <20221028181430.GA2079477@roeck-us.net>
Thanks Nathan for the fix.
- Quan
On 29/10/2022 01:14, Guenter Roeck wrote:
> On Thu, Oct 27, 2022 at 04:16:12PM -0700, Nathan Chancellor wrote:
>> Clang warns:
>>
>> drivers/hwmon/smpro-hwmon.c:378:2: error: unannotated fall-through between switch labels [-Werror,-Wimplicit-fallthrough]
>> default:
>> ^
>> drivers/hwmon/smpro-hwmon.c:378:2: note: insert 'break;' to avoid fall-through
>> default:
>> ^
>> break;
>> 1 error generated.
>>
>> Clang is a little more pedantic than GCC, which does not warn when
>> falling through to a case that is just break or return. Clang's version
>> is more in line with the kernel's own stance in deprecated.rst, which
>> states that all switch/case blocks must end in either break,
>> fallthrough, continue, goto, or return.
>>
>> Add the missing break to silence the warning. Additionally, adjust the
>> indentation of a break and add a default case to the inner switch
>> statement.
>>
>> Fixes: a87456864cbb ("hwmon: Add Ampere's Altra smpro-hwmon driver")
>> Link: https://github.com/ClangBuiltLinux/linux/issues/1751
>> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
>
> Applied.
>
> Thanks,
> Guenter
>
>> ---
>>
>> v2:
>>
>> * Add missing default case to inner switch statement (Guenter)
>> * Fix indentation of break in inner switch statement (Guenter)
>> * Reword commit message to include these changes
>>
>> v1: https://lore.kernel.org/20221027195238.1789586-1-nathan@kernel.org/
>>
>> drivers/hwmon/smpro-hwmon.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>>
>> base-commit: 0ffb687b6508c36a17b99bdaf014b38532404182
>>
>> diff --git a/drivers/hwmon/smpro-hwmon.c b/drivers/hwmon/smpro-hwmon.c
>> index ee54e21c2c12..a76c49dd8438 100644
>> --- a/drivers/hwmon/smpro-hwmon.c
>> +++ b/drivers/hwmon/smpro-hwmon.c
>> @@ -373,8 +373,11 @@ static umode_t smpro_is_visible(const void *data, enum hwmon_sensor_types type,
>> ret = regmap_read(hwmon->regmap, temperature[channel].reg, &value);
>> if (ret || value == 0xFFFF)
>> return 0;
>> - break;
>> + break;
>> + default:
>> + break;
>> }
>> + break;
>> default:
>> break;
>> }
prev parent reply other threads:[~2022-10-29 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 23:16 Nathan Chancellor
2022-10-28 18:14 ` Guenter Roeck
2022-10-29 8:49 ` Quan Nguyen [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=0ea97349-afad-e0ab-09c7-f61c782555a0@os.amperecomputing.com \
--to=quan@os.amperecomputing.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=patches@lists.linux.dev \
--cc=trix@redhat.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®