[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191008130234.GP2294@hirez.programming.kicks-ass.net>
Date: Tue, 8 Oct 2019 15:02:34 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Dietmar Eggemann <dietmar.eggemann@....com>
Cc: Vincent Guittot <vincent.guittot@...aro.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>, Phil Auld <pauld@...hat.com>,
Valentin Schneider <valentin.schneider@....com>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Quentin Perret <quentin.perret@....com>,
Morten Rasmussen <Morten.Rasmussen@....com>,
Hillf Danton <hdanton@...a.com>
Subject: Re: [PATCH v3 04/10] sched/fair: rework load_balance
On Wed, Oct 02, 2019 at 11:21:20AM +0200, Dietmar Eggemann wrote:
> I thought we should always order local variable declarations from
> longest to shortest line but can't find this rule in coding-style.rst
> either.
You're right though, that is generally encouraged. From last years
(2018) KS there was the notion of a subsystem handbook and the tip
tree's submissions thereto can be found there:
https://lore.kernel.org/lkml/20181107171149.165693799@linutronix.de/
But for some raisin that never actually went anywhere...
Powered by blists - more mailing lists