From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: cortex-a7: move proc_info out of !CONFIG_ARM_LPAE block
Date: Tue, 17 Jan 2012 12:14:14 +0000 [thread overview]
Message-ID: <20120117121413.GD11475@arm.com> (raw)
In-Reply-To: <1326740096-6409-1-git-send-email-will.deacon@arm.com>
On Mon, Jan 16, 2012 at 06:54:56PM +0000, Will Deacon wrote:
> The merging of commits 1b6ba46b ("ARM: LPAE: MMU setup for the 3-level
> page table format") and b4244738 ("ARM: 7202/1: Add Cortex-A7 proc info")
> during the merge window ended up putting the Cortex-A7 proc_info into a
> code block guarded by !CONFIG_ARM_LPAE. This makes Cortex-A7 platforms
> unbootable when LPAE is enabled.
>
> This patch moves the proc_info structure for Cortex-A7 outside of the
> guarded block.
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Pawel Moll <pawel.moll@arm.com>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
--
Catalin
prev parent reply other threads:[~2012-01-17 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 18:54 [PATCH] ARM: cortex-a7: move proc_info out of !CONFIG_ARM_LPAE block Will Deacon
2012-01-17 12:14 ` Catalin Marinas [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=20120117121413.GD11475@arm.com \
--to=catalin.marinas@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 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).