[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANDhNCpL1S0s0nLfWKsHF+59kaO1Aj5N3NbEYMgazHVaRwJX9g@mail.gmail.com>
Date: Tue, 26 Apr 2022 13:41:25 -0700
From: John Stultz <jstultz@...gle.com>
To: "Maciej W. Rozycki" <macro@...am.me.uk>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Stephen Boyd <sboyd@...nel.org>,
Russell King <linux@...linux.org.uk>,
Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] sched_clock: Fix formatting of frequency reporting code
On Sun, Apr 24, 2022 at 4:47 AM Maciej W. Rozycki <macro@...am.me.uk> wrote:
>
> Use flat rather than nested indentation for chained else/if clauses as
> per coding-style.rst:
>
> if (x == y) {
> ..
> } else if (x > y) {
> ...
> } else {
> ....
> }
>
> This also improves readability.
>
> Signed-off-by: Maciej W. Rozycki <macro@...am.me.uk>
> Fixes: 32fea568aec5b ("timers, sched/clock: Clean up the code a bit")
This patch seems fine to me. Though as Ingo was the one to introduce
the change, his style preference may override in this case.
Acked-by: John Stultz <jstultz@...gle.com>
thanks
-john
Powered by blists - more mailing lists