[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d570866d-8d2d-3d6b-e0b0-5139e7b990e4@acm.org>
Date: Fri, 28 Jan 2022 12:30:13 -0800
From: Bart Van Assche <bvanassche@....org>
To: Joe Perches <joe@...ches.com>, Tom Rix <trix@...hat.com>,
kashyap.desai@...adcom.com, sumit.saxena@...adcom.com,
shivasharan.srikanteshwara@...adcom.com, jejb@...ux.ibm.com,
martin.petersen@...cle.com, nathan@...nel.org,
ndesaulniers@...gle.com
Cc: megaraidlinux.pdl@...adcom.com, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH] scsi: megaraid: cleanup formatting of megaraid
On 1/28/22 11:11, Joe Perches wrote:
> On Fri, 2022-01-28 at 09:59 -0800, Tom Rix wrote:
>> On 1/28/22 9:42 AM, Bart Van Assche wrote:
>>> Isn't this the kind of patches that carries more risk than value?
>
> Risk for whitespace style reformatting patches is quite low.
But the annoyance factor for patches that reformat an entire source file
is very high. It forces everyone who has conflicting patches pending to
wait until the reformatting patch went in, rebase their tree and also to
resolve the complicated merge conflicts that are the result of the
reformatting patch. I have already had to do this several times in the past.
Thanks,
Bart.
Powered by blists - more mailing lists