[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eecb7c3e-88b2-ec2f-0235-280da51ae69c@redhat.com>
Date: Sun, 18 Oct 2020 07:04:49 -0700
From: Tom Rix <trix@...hat.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: 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,
linux-crypto@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-power@...rohmeurope.com, linux-gpio@...r.kernel.org,
amd-gfx@...ts.freedesktop.org, 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, netdev@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, ath10k@...ts.infradead.org,
linux-wireless@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com, linux-nfc@...ts.01.org,
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@...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@...glegroups.com
Subject: Re: [RFC] treewide: cleanup unreachable breaks
On 10/17/20 10:43 PM, Greg KH 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.
OK.
Thanks,
Tom
>
> Sending us a patch, without even a diffstat to review, isn't going to
> get you very far...
>
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists