[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161129135017.GL3092@twins.programming.kicks-ass.net>
Date: Tue, 29 Nov 2016 14:50:17 +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:39:20PM +0100, Geert Uytterhoeven wrote:
> > Not understanding, why would a user ever need it? The platform knows if
> > its has funny boot image size limits, no?
>
> The boot loader does not come with the kernel, so the platform cannot
> know for sure.
Why would anybody use a bootloader that imposes weird restrictions on
their platform? That is, isn't that simply a broken bootloader?
Powered by blists - more mailing lists