Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752273Ab3HDMx5 (ORCPT ); Sun, 4 Aug 2013 08:53:57 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:40250 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751649Ab3HDMx4 (ORCPT ); Sun, 4 Aug 2013 08:53:56 -0400 Date: Sun, 4 Aug 2013 13:53:46 +0100 From: Russell King - ARM Linux To: Olof Johansson Cc: "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: Build breakage due to latest ARM fixes Message-ID: <20130804125346.GH23006@n2100.arm.linux.org.uk> References: <20130803000731.GS23006@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130803000731.GS23006@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1002 Lines: 19 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. 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/