linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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/  |

      reply	other threads:[~2014-06-02  7:19 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
2014-05-30  8:02     ` Uwe Kleine-König
2014-06-02  7:19       ` Uwe Kleine-König [this message]

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=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).