[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201122220540.GC566387@ravnborg.org>
Date: Sun, 22 Nov 2020 23:05:40 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: "Gustavo A. R. Silva" <gustavoars@...nel.org>
Cc: Andres Salomon <dilinger@...ued.net>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
linux-fbdev@...r.kernel.org, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org, linux-geode@...ts.infradead.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH 134/141] video: fbdev: lxfb_ops: Fix fall-through
warnings for Clang
Hi Gustavo,
On Fri, Nov 20, 2020 at 12:40:32PM -0600, Gustavo A. R. Silva wrote:
> In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
> by explicitly adding a break statement instead of letting the code fall
> through to the next case.
>
> Link: https://github.com/KSPP/linux/issues/115
> Signed-off-by: Gustavo A. R. Silva <gustavoars@...nel.org>
Thanks, applied this and the following patch to drm-misc-next.
Looks forward to have this warning enabled.
One can only wonder how many hours will be saved by lettting the
compiler tell you a break is missing. This is the kind of bugs you can
stare you blind at.
Sam
Powered by blists - more mailing lists