[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 4 Mar 2022 00:17:25 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Finn Thain <fthain@...ux-m68k.org>
Cc: Konrad Wilhelm Kleine <kkleine@...hat.com>,
Tom Rix <trix@...hat.com>, Joe Perches <joe@...ches.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 Thu, Mar 3, 2022 at 11:44 PM Finn Thain <fthain@...ux-m68k.org> wrote:
>
> Others might argue that they should always be changed from,
>
> /*
> * this style
> * of multiline comment
> */
>
> to
>
> /* this style
> * of multiline comment
> */
In general, for things that the coding style guide talks about, we
should follow them, even if some subsystems do not (they can always
override in their folder if they really, really want it). So, here for
instance, the first one should be used.
Cheers,
Miguel
Powered by blists - more mailing lists