[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d519b20b-694a-d8a7-66ed-1c5961590d4b@digikod.net>
Date: Wed, 11 May 2022 19:34:09 +0200
From: Mickaël Salaün <mic@...ikod.net>
To: Joe Perches <joe@...ches.com>, Miguel Ojeda <ojeda@...nel.org>
Cc: Andy Whitcroft <apw@...onical.com>,
Brian Norris <briannorris@...omium.org>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
"Jason A . Donenfeld" <Jason@...c4.com>,
Kees Cook <keescook@...omium.org>,
Konstantin Meskhidze <konstantin.meskhidze@...wei.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Paul Moore <paul@...l-moore.com>, Tom Rix <trix@...hat.com>,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH v2 5/5] clang-format: Fix space after for_each macros
On 11/05/2022 17:40, Joe Perches wrote:
> On Fri, 2022-05-06 at 18:01 +0200, Mickaël Salaün wrote:
>> Set SpaceBeforeParens to ControlStatementsExceptForEachMacros to not add
>> space between a for_each macro and the following parenthesis. This
>> option is available since clang-format-11 [1] and is in line with the
>> checkpatch.pl rules [2].
>
> If this is applied, could the .clang_format ForEachMacros:
> block be removed?
The ForEachMacros block is still required to not put the " {" on the
next line.
Powered by blists - more mailing lists