[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201019230546.GH36674@ziepe.ca>
Date: Mon, 19 Oct 2020 20:05:46 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Tom Rix <trix@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
linux-edac@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-pm@...r.kernel.org, xen-devel@...ts.xenproject.org,
linux-block@...r.kernel.org,
openipmi-developer@...ts.sourceforge.net,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-power@...rohmeurope.com, linux-gpio@...r.kernel.org,
amd-gfx list <amd-gfx@...ts.freedesktop.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
nouveau@...ts.freedesktop.org,
virtualization@...ts.linux-foundation.org,
spice-devel@...ts.freedesktop.org, linux-iio@...r.kernel.org,
linux-amlogic@...ts.infradead.org,
industrypack-devel@...ts.sourceforge.net,
linux-media@...r.kernel.org, MPT-FusionLinux.pdl@...adcom.com,
linux-scsi@...r.kernel.org, linux-mtd@...ts.infradead.org,
linux-can@...r.kernel.org,
Network Development <netdev@...r.kernel.org>,
intel-wired-lan@...ts.osuosl.org, ath10k@...ts.infradead.org,
linux-wireless <linux-wireless@...r.kernel.org>,
linux-stm32@...md-mailman.stormreply.com, linux-nfc@...ts.01.org,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
linux-pci@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
platform-driver-x86@...r.kernel.org, patches@...nsource.cirrus.com,
storagedev@...rochip.com, devel@...verdev.osuosl.org,
linux-serial@...r.kernel.org, linux-usb@...r.kernel.org,
usb-storage@...ts.one-eyed-alien.net,
linux-watchdog@...r.kernel.org, ocfs2-devel@....oracle.com,
bpf <bpf@...r.kernel.org>, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
alsa-devel@...a-project.org,
clang-built-linux <clang-built-linux@...glegroups.com>,
Greg KH <gregkh@...uxfoundation.org>,
George Burgess <gbiv@...gle.com>
Subject: Re: [RFC] treewide: cleanup unreachable breaks
On Mon, Oct 19, 2020 at 12:42:15PM -0700, Nick Desaulniers wrote:
> On Sat, Oct 17, 2020 at 10:43 PM Greg KH <gregkh@...uxfoundation.org> wrote:
> >
> > On Sat, Oct 17, 2020 at 09:09:28AM -0700, trix@...hat.com wrote:
> > > From: Tom Rix <trix@...hat.com>
> > >
> > > This is a upcoming change to clean up a new warning treewide.
> > > I am wondering if the change could be one mega patch (see below) or
> > > normal patch per file about 100 patches or somewhere half way by collecting
> > > early acks.
> >
> > Please break it up into one-patch-per-subsystem, like normal, and get it
> > merged that way.
> >
> > Sending us a patch, without even a diffstat to review, isn't going to
> > get you very far...
>
> Tom,
> If you're able to automate this cleanup, I suggest checking in a
> script that can be run on a directory. Then for each subsystem you
> can say in your commit "I ran scripts/fix_whatever.py on this subdir."
> Then others can help you drive the tree wide cleanup. Then we can
> enable -Wunreachable-code-break either by default, or W=2 right now
> might be a good idea.
I remember using clang-modernize in the past to fix issues very
similar to this, if clang machinery can generate the warning, can't
something like clang-tidy directly generate the patch?
You can send me a patch for drivers/infiniband/* as well
Thanks,
Jason
Powered by blists - more mailing lists