[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f9b3b4377768249febf62bb5d5c5f5b6197f627f.camel@perches.com>
Date: Wed, 24 Oct 2018 03:24:44 -0700
From: Joe Perches <joe@...ches.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Jacek Anaszewski <jacek.anaszewski@...il.com>,
Dan O'Donovan <dan@...tex.com>, linux-kernel@...r.kernel.org,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
Pavel Machek <pavel@....cz>, linux-gpio@...r.kernel.org,
linux-leds@...r.kernel.org,
Carlos Iglesias <carlos.iglesias@...tex.com>,
Javier Arteaga <javier@...tex.com>
Subject: Re: [PATCH v2 2/3] leds: upboard: Add LED support
On Wed, 2018-10-24 at 13:13 +0300, Andy Shevchenko wrote:
> On Tue, Oct 23, 2018 at 12:23:13PM -0700, Joe Perches wrote:
> > Until such a time when either a local preferred style
> > document or a treewide preferred style exists, please
> > stop asking people to modify #include ordering for
> > various styles like reverse christmas tree by length,
> > alphabetic ordering, or other individual styles.
>
> Why? It makes a sense to ask for new code (and even for patches against old one in some cases).
It's just a nit and frequently impossible to require as
ordering dependencies between include files do exist.
> > My preferred style would always have kernel.h first
> > as that may help with precompiled headers and overall
> > kernel compilation time one day.
>
> How ordering would screw this up?
gcc has many limits on the use of precompiled headers.
https://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html
Precompiled headers are often shared by multiple
compilation units and precompilation can be stopped
after a specific header.
Powered by blists - more mailing lists