linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Build breakage due to latest ARM fixes
Date: Sun, 4 Aug 2013 13:53:46 +0100	[thread overview]
Message-ID: <20130804125346.GH23006@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130803000731.GS23006@n2100.arm.linux.org.uk>

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.

  parent reply	other threads:[~2013-08-04 12:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 23:41 Build breakage due to latest ARM fixes Olof Johansson
2013-08-03  0:07 ` Russell King - ARM Linux
2013-08-03  0:24   ` Olof Johansson
2013-08-03  0:41     ` Russell King - ARM Linux
2013-08-03  0:48       ` Russell King - ARM Linux
2013-08-03  2:14         ` Olof Johansson
2013-08-03  0:57     ` Russell King - ARM Linux
2013-08-04 12:53   ` Russell King - ARM Linux [this message]
2013-08-04 18:20     ` Olof Johansson
2013-08-04 18:37       ` Russell King - ARM Linux
2013-08-04 18:47         ` Olof Johansson
2013-08-04 19:01           ` Russell King - ARM Linux
2013-08-04 19:19             ` Olof Johansson
2013-08-04 19:36           ` Uwe Kleine-König
2013-08-05  9:45             ` Jonathan Austin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130804125346.GH23006@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).