All of lore.kernel.org
 help / color / mirror / Atom feed
From: jonathan.austin@arm.com (Jonathan Austin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mpu: Ensure that MPU depends on CPU_V7
Date: Fri, 07 Jun 2013 19:20:42 +0100	[thread overview]
Message-ID: <51B2247A.1040504@arm.com> (raw)
In-Reply-To: <20130607181126.GA11232@pengutronix.de>

On 07/06/13 19:11, Uwe Kleine-K?nig wrote:
> On Fri, Jun 07, 2013 at 06:17:53PM +0100, Jonathan Austin wrote:
>> The support for the MPU is currently implemented only for R-class
>> (PMSAv7/R). Since the merge of V7M support in to the kernel it is possible
>> to select MPU support on V7M.
>>
>> This patch ensures that until MPU support for M-class processors is
>> implemented, the MPU can only be selected with R-class CPUs
>>
>> Signed-off-by: Jonathan Austin <jonathan.austin@arm.com>
>> Cc: Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>
>> ---
>>
>> This patch is necessary now that Russell has merged the V7M work in to his
>> devel-stable branch.
>>
>> I don't have any immediate plans to implement MPU support for M-class, so this
>> patch is important to ensure we don't break building of V7M platforms.
> Acked-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
>
> I didn't check, but that might affect other nommu configs for pre-v7
> cpu's, too. (I think there is support for an at91 in the tree?!)
>

Thanks Uwe,

You're right - I just checked and without this patch we cause issues 
with at91x40_defconfig. This patch *does* fix that too.

I've added your acked-by and this time I've got the '?' :)

Jonny

      reply	other threads:[~2013-06-07 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 17:17 [PATCH] ARM: mpu: Ensure that MPU depends on CPU_V7 Jonathan Austin
2013-06-07 18:11 ` Uwe Kleine-König
2013-06-07 18:20   ` Jonathan Austin [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=51B2247A.1040504@arm.com \
    --to=jonathan.austin@arm.com \
    --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 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.