[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9989e7d048765111826d1df549a364485ea546f.camel@perches.com>
Date: Tue, 17 Nov 2020 08:15:59 -0800
From: Joe Perches <joe@...ches.com>
To: "Gustavo A. R. Silva" <gustavoars@...nel.org>,
Amitkumar Karwar <amitkarwar@...il.com>,
Ganapathi Bhat <ganapathi.bhat@....com>,
Xinming Hu <huxinming820@...il.com>,
Kalle Valo <kvalo@...eaurora.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>
Cc: linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH][next] mwifiex: Fix fall-through warnings for Clang
On Tue, 2020-11-17 at 10:09 -0600, Gustavo A. R. Silva wrote:
> In preparation to enable -Wimplicit-fallthrough for Clang, fix multiple
> warnings by explicitly adding multiple break statements instead of
> letting the code fall through to the next case.
Thanks Gustavo.
I think this is better style than the gcc allowed
undescribed fallthrough to break;
gcc developers disagree though:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91432
Powered by blists - more mailing lists