From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: nommu build failures on ARM in linux-next
Date: Fri, 30 May 2014 09:58:30 +0200 [thread overview]
Message-ID: <20140530075830.GO22169@pengutronix.de> (raw)
In-Reply-To: <20140529234012.GL3693@n2100.arm.linux.org.uk>
On Fri, May 30, 2014 at 12:40:12AM +0100, Russell King - ARM Linux wrote:
> Even so, I suspect even with this build problem solved, that's not going
> to be the end of the story for noMMU breakage... it's certainly something
> that gets very little testing by anyone. I suspect it should be removed
> from the mainline kernel tree rather than being a constant source of these
> kinds of problems.
Uwe can have a look next week.
Taken that it took *ages* to get Cortex-M3 support in mainline and taken
that it might become more interesting with the upcoming generation of
FPGAs and Cortex-A SoCs with an additional Cortex-M, it would be pretty
bad to lose NOMMU again.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2014-05-30 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 16:53 nommu build failures on ARM in linux-next Paul Gortmaker
2014-05-29 18:55 ` Russell King - ARM Linux
2014-05-29 23:40 ` Russell King - ARM Linux
2014-05-30 0:05 ` Paul Gortmaker
2014-05-30 7:58 ` Robert Schwebel [this message]
2014-05-30 8:02 ` Uwe Kleine-König
2014-06-02 7:19 ` Uwe Kleine-König
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=20140530075830.GO22169@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--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).