From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Olof Johansson <olof@lixom.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Build breakage due to latest ARM fixes
Date: Sun, 4 Aug 2013 19:37:08 +0100 [thread overview]
Message-ID: <20130804183708.GI23006@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMhNr5-6T9s8Y9jr2pWy=baceuZwGFNj2HtnqU9DbwPLvw@mail.gmail.com>
On Sun, Aug 04, 2013 at 11:20:21AM -0700, Olof Johansson wrote:
> On Sun, Aug 4, 2013 at 5:53 AM, Russell King - ARM Linux
> <linux@arm.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?
No, they've had no testing as far as I'm aware. noMMU never got to the
stage when it was merged that it had any platforms before Hiyok went
silent.
The only real testing I'm aware of is when I recreated the OKI67001
support a while back and got my board to boot.
As for qemu, software emulations while nice and convenient don't
accurately reflect real hardware.
next prev parent reply other threads:[~2013-08-04 18:37 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
2013-08-04 18:20 ` Olof Johansson
2013-08-04 18:37 ` Russell King - ARM Linux [this message]
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=20130804183708.GI23006@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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