From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jonathan Austin <Jonathan.Austin@arm.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
kernel@pengutronix.de,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: nommu build failures on ARM in linux-next
Date: Mon, 2 Jun 2014 09:19:05 +0200 [thread overview]
Message-ID: <20140602071905.GD11207@pengutronix.de> (raw)
In-Reply-To: <20140530080257.GW20155@pengutronix.de>
Hello,
On Fri, May 30, 2014 at 10:02:57AM +0200, Uwe Kleine-König 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.
> That would mean that support for Cortex-M3 would die, too, which would
> (IMHO) be sad.
Just for your information: The problem in question here doesn't affect
ARM-v7M (aka Cortex-M[34]) because the patch only touches areas
protected by #ifdef CONFIG_CPU_CP15 which is off for these machines.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
WARNING: multiple messages have this Message-ID (diff)
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: nommu build failures on ARM in linux-next
Date: Mon, 2 Jun 2014 09:19:05 +0200 [thread overview]
Message-ID: <20140602071905.GD11207@pengutronix.de> (raw)
In-Reply-To: <20140530080257.GW20155@pengutronix.de>
Hello,
On Fri, May 30, 2014 at 10:02:57AM +0200, Uwe Kleine-K?nig 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.
> That would mean that support for Cortex-M3 would die, too, which would
> (IMHO) be sad.
Just for your information: The problem in question here doesn't affect
ARM-v7M (aka Cortex-M[34]) because the patch only touches areas
protected by #ifdef CONFIG_CPU_CP15 which is off for these machines.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-06-02 7:19 UTC|newest]
Thread overview: 14+ 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 16:53 ` Paul Gortmaker
2014-05-29 18:55 ` Russell King - ARM Linux
2014-05-29 18:55 ` Russell King - ARM Linux
2014-05-29 23:40 ` Russell King - ARM Linux
2014-05-29 23:40 ` Russell King - ARM Linux
2014-05-30 0:05 ` Paul Gortmaker
2014-05-30 0:05 ` Paul Gortmaker
2014-05-30 7:58 ` Robert Schwebel
2014-05-30 7:58 ` Robert Schwebel
2014-05-30 8:02 ` Uwe Kleine-König
2014-05-30 8:02 ` Uwe Kleine-König
2014-06-02 7:19 ` Uwe Kleine-König [this message]
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=20140602071905.GD11207@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Jonathan.Austin@arm.com \
--cc=kernel@pengutronix.de \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul.gortmaker@windriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.