[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220330161950.1d12d708@gandalf.local.home>
Date: Wed, 30 Mar 2022 16:19:50 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: Ingo Molnar <mingo@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH v2] ftrace: Make ftrace_graph_is_dead() a static branch
On Wed, 30 Mar 2022 06:55:26 +0000
Christophe Leroy <christophe.leroy@...roup.eu> wrote:
> > Small nit. Please order the includes in "upside-down x-mas tree" fashion:
> >
> > #include <linux/jump_label.h>
> > #include <linux/suspend.h>
> > #include <linux/ftrace.h>
> > #include <linux/slab.h>
> >
>
> That's the first time I get such a request. Usually people request
> #includes to be in alphabetical order so when I see a file that has
> headers in alphabetical order I try to not break it, but here that was
> not the case so I put it at the end of the list.
This is something that Ingo Molnar started back in 2009 or so. And I do
find it easier on the eyes ;-) I may be the only one today trying to keep
it (albeit poorly).
It's not a hard requirement, but I find it makes the code look more like
art, which it is :-D
>
> I'll send v3
Thanks,
-- Steve
Powered by blists - more mailing lists