[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250211181442.GB2995885@ax162>
Date: Tue, 11 Feb 2025 13:14:42 -0500
From: Nathan Chancellor <nathan@...nel.org>
To: Michael Riesch <michael.riesch@...fvision.net>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev
Subject: Re: [PATCH 2/2] clang-format: align consecutive macros
On Mon, Feb 10, 2025 at 09:21:01AM +0100, Michael Riesch wrote:
> clang-format 9 introduced the option "AlignConsecutiveMacros".
> Set it to "AcrossEmptyLinesAndComments" in order to avoid macro
> definitions of the form:
>
> #define MAGIC_REGISTER_1 0x42
> #define MAGIC_REGISTER_BIT_FLIP BIT(2)
> /* important comment */
> #define MAGIC_REGISTER_BIT_ENABLE BIT(12)
>
> #define MAGIC_REGISTER_2 0x43
>
> With the option set to "AcrossEmptyLinesAndComments", they will
> be converted to
>
> #define MAGIC_REGISTER_1 0x42
> #define MAGIC_REGISTER_BIT_FLIP BIT(2)
> /* important comment */
> #define MAGIC_REGISTER_BIT_ENABLE BIT(12)
>
> #define MAGIC_REGISTER_2 0x43
>
> which seems to be the convention in the kernel code base.
>
> Signed-off-by: Michael Riesch <michael.riesch@...fvision.net>
I could see this being controversial in some cases but let's see what
happens.
Reviewed-by: Nathan Chancellor <nathan@...nel.org>
> ---
> .clang-format | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.clang-format b/.clang-format
> index 8040b516185b..30d09cb88170 100644
> --- a/.clang-format
> +++ b/.clang-format
> @@ -13,6 +13,7 @@ AccessModifierOffset: -4
> AlignAfterOpenBracket: Align
> AlignConsecutiveAssignments: false
> AlignConsecutiveDeclarations: false
> +AlignConsecutiveMacros: AcrossEmptyLinesAndComments
> AlignEscapedNewlines: Left
> AlignOperands: true
> AlignTrailingComments: false
>
> --
> 2.34.1
>
Powered by blists - more mailing lists