[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.21.1810040915040.8@nippy.intranet>
Date: Thu, 4 Oct 2018 09:27:16 +1000 (AEST)
From: Finn Thain <fthain@...egraphics.com.au>
To: Leonardo Bras <leobras.c@...il.com>
cc: Robert Richter <rric@...nel.org>, lkcamp@...ts.libreplanetbr.org,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
"James E.J. Bottomley" <jejb@...isc-linux.org>,
Helge Deller <deller@....de>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-m68k@...ts.linux-m68k.org, oprofile-list@...ts.sf.net,
linux-parisc@...r.kernel.org, linux-s390@...r.kernel.org,
James Bottomley <James.Bottomley@...senpartnership.com>
Subject: Re: [PATCH v3 0/7] Remove errors building drivers/DRIVERNAME
On Wed, 3 Oct 2018, Leonardo Bras wrote:
>
> Sorry, I was not very clear at my reasons why this change is important,
> I will try to briefly explain the whole story.
>
> Some weeks ago I was trying to solve a task that needed to change some
> compiling options, build the whole kernel (allyesconfig) and look for
> errors. The problem was: It would take a long time to build everything
> in my computer. And many friends with slimmer laptops would take much
> longer.
>
It seems to me that you shouldn't need expensive optimization for
continuous integration. In theory that could make a big difference though
I admit to no experience of build farms.
Have you looked at ccache? It will save you from having to recompile any
files not changed.
You could also leverage all of your laptops together using distcc.
HTH.
--
Powered by blists - more mailing lists