[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72noan-b84yU370wVaRRu-GX=A5X0Ocfv4uJDk2nyeR0aw@mail.gmail.com>
Date: Fri, 4 Mar 2022 13:31:48 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: Finn Thain <fthain@...ux-m68k.org>,
Konrad Wilhelm Kleine <kkleine@...hat.com>,
Tom Rix <trix@...hat.com>,
Bart Van Assche <bvanassche@....org>,
kashyap.desai@...adcom.com, sumit.saxena@...adcom.com,
shivasharan.srikanteshwara@...adcom.com, jejb@...ux.ibm.com,
martin.petersen@...cle.com, Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
megaraidlinux.pdl@...adcom.com, scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>, llvm@...ts.linux.dev
Subject: Re: [PATCH] scsi: megaraid: cleanup formatting of megaraid
On Fri, Mar 4, 2022 at 5:03 AM Joe Perches <joe@...ches.com> wrote:
>
> It's up to individual maintainers to each decide on what might be
> considered unnecessary churn for the subsystems they control.
>
> One argument is that churn leads to difficulty in backporting
> fixes to older 'stable' versions.
>
> I think the churn argument is overstated.
I was only pointing out that, for the global `.clang-format` file, the
style in `coding-style.rst` should be followed. Then subsystem
maintainers may override it if really needed.
I definitely agree that we should aim to have a consistent style.
However, by allowing a few exceptions, some major subsystems may start
using `clang-format` sooner.
Cheers,
Miguel
Powered by blists - more mailing lists