[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161129133141.GK3092@twins.programming.kicks-ass.net>
Date: Tue, 29 Nov 2016 14:31:41 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Babu Moger <babu.moger@...cle.com>, Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Dan Williams <dan.j.williams@...el.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Tejun Heo <tj@...nel.org>, Sam Ravnborg <sam@...nborg.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
sparclinux <sparclinux@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH v3 0/2] Ajust lockdep static allocations for sparc
On Tue, Nov 29, 2016 at 02:26:47PM +0100, Geert Uytterhoeven wrote:
> On Tue, Nov 29, 2016 at 1:29 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> > On Tue, Nov 29, 2016 at 12:52:04PM +0100, Geert Uytterhoeven wrote:
> >> Not because of platforms with not limited memory, but because of platforms
> >> with boot loaders that have silly kernel size limitations, and start
> >> scribbling over the DTB or even theirselves when copying a large kernel image.
> >
> > Right, that's the weird platforms clause above, and those can select the
> > option.
>
> Their Kconfig files can select it. The users can't.
> What about making it visible depending on EXPERT?
Not understanding, why would a user ever need it? The platform knows if
its has funny boot image size limits, no?
Powered by blists - more mailing lists