linux-kernel - Re: Build breakage due to latest ARM fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 4 Aug 2013 11:20:21 -0700
From:	Olof Johansson <olof@...om.net>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Build breakage due to latest ARM fixes

On Sun, Aug 4, 2013 at 5:53 AM, Russell King - ARM Linux
<linux@....linux.org.uk> wrote:
> On Sat, Aug 03, 2013 at 01:07:31AM +0100, Russell King - ARM Linux wrote:
>> I'll look into that.  Obviously, I never build nommu because it isn't
>> part of the build system and the nommu platform I do have - OKI67001 -
>> doesn't have mainline kernel support.  (And if it did, it would not be
>> DT, so I doubt it's submittable.)
>
> Okay, what I'm going to do is push the OKI67001 stuff into mainline
> irrespective of DT or not, so that I can then add noMMU build _and_
> boot tests to my build system, which should ensure that problems
> like that get detected before they're pushed upstream.

That seems like a step backwards. How have !MMU changes been handled
until now? Someone external has been relied on for testing?

> If people want me to care about noMMU, that's what has to happen
> because I have no other noMMU platform - if not, people can put up with
> noMMU breaking from time to time.

It seems that qemu has a couple of the stellaris platforms supported,
but as usual I suspect they can't be relied on to actually work.


-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/