[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250630075638.GJ1613200@noisy.programming.kicks-ass.net>
Date: Mon, 30 Jun 2025 09:56:38 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Alexander Potapenko <glider@...gle.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, quic_jiangenj@...cinc.com,
linux-kernel@...r.kernel.org, kasan-dev@...glegroups.com,
Aleksandr Nogikh <nogikh@...gle.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Dmitry Vyukov <dvyukov@...gle.com>, Ingo Molnar <mingo@...hat.com>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Marco Elver <elver@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v2 02/11] kcov: apply clang-format to kcov code
On Fri, Jun 27, 2025 at 02:50:18PM +0200, Alexander Potapenko wrote:
> Setting AlignConsecutiveDeclarations: AcrossEmptyLinesAndComments will
> replace the above with the following diff:
>
> struct kcov_percpu_data {
> - void *irq_area;
> - local_lock_t lock;
> -
> - unsigned int saved_mode;
> - unsigned int saved_size;
> - void *saved_area;
> - struct kcov *saved_kcov;
> - int saved_sequence;
> + void *irq_area;
> + local_lock_t lock;
> +
> + unsigned int saved_mode;
> + unsigned int saved_size;
> + void *saved_area;
> + struct kcov *saved_kcov;
> + int saved_sequence;
> };
>
> (a bit denser, plus it aligns the variable names, not the pointer signs)
> Does this look better?
Better yes, but still not really nice.
Powered by blists - more mailing lists