[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51A5FE2D.9080403@synopsys.com>
Date: Wed, 29 May 2013 18:40:05 +0530
From: Vineet Gupta <Vineet.Gupta1@...opsys.com>
To: Max Filippov <jcmvbkbc@...il.com>
CC: lkml <linux-kernel@...r.kernel.org>
Subject: Fwd: [PATCH 2/2] xtensa: Flat DeviceTree copy not future-safe
Hi Max,
This patch - acked by you then, got lost in the mist of time. Care to take it in
via xtensa tree for 3.11
Thx,
-Vineet
-------- Original Message --------
Subject: [PATCH 2/2] xtensa: Flat DeviceTree copy not future-safe
Date: Fri, 22 Feb 2013 00:09:22 +0530
From: Vineet Gupta <Vineet.Gupta1@...opsys.com>
To: Andrew Morton <akpm@...ux-foundation.org>, Chris Zankel <chris@...kel.net>,
Max Filippov <jcmvbkbc@...il.com>, Marc Gauthier <marc@...silica.com>
CC: Vineet Gupta <Vineet.Gupta1@...opsys.com>, <linux-xtensa@...ux-xtensa.org>,
<linux-kernel@...r.kernel.org>
Newsgroups: gmane.linux.kernel
References: <1361471962-25164-1-git-send-email-vgupta@...opsys.com>
flat DT copy code calls bootmem allocator with @align = 0.
This is probably OK with legacy allocator which xtensa uses right now,
but this will panic right away with memblock allocator
Signed-off-by: Vineet Gupta <vgupta@...opsys.com>
Cc: Chris Zankel <chris@...kel.net>
Cc: Max Filippov <jcmvbkbc@...il.com>
Cc: Marc Gauthier <marc@...silica.com>
Cc: linux-xtensa@...ux-xtensa.org
Cc: linux-kernel@...r.kernel.org
---
arch/xtensa/kernel/setup.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/xtensa/kernel/setup.c b/arch/xtensa/kernel/setup.c
index 6dd25ec..c2a526e 100644
--- a/arch/xtensa/kernel/setup.c
+++ b/arch/xtensa/kernel/setup.c
@@ -256,7 +256,7 @@ void __init early_init_devtree(void *params)
static void __init copy_devtree(void)
{
void *alloc = early_init_dt_alloc_memory_arch(
- be32_to_cpu(initial_boot_params->totalsize), 0);
+ be32_to_cpu(initial_boot_params->totalsize), 8);
if (alloc) {
memcpy(alloc, initial_boot_params,
be32_to_cpu(initial_boot_params->totalsize));
--
1.7.4.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists