[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1470988871-2799-4-git-send-email-jszhang@marvell.com>
Date: Fri, 12 Aug 2016 16:01:10 +0800
From: Jisheng Zhang <jszhang@...vell.com>
To: <catalin.marinas@....com>, <will.deacon@....com>,
<lorenzo.pieralisi@....com>, <keescook@...omium.org>,
<mark.rutland@....com>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, Jisheng Zhang <jszhang@...vell.com>
Subject: [PATCH v3 3/4] arm64: kaslr: Fix incorrect placement of __initdata and __read_mostly
__initdata and __read_mostly should be placed after the variable name
for the variable to be placed in the intended section.
Signed-off-by: Jisheng Zhang <jszhang@...vell.com>
---
arch/arm64/kernel/kaslr.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/kernel/kaslr.c b/arch/arm64/kernel/kaslr.c
index b054691..8ebabc4 100644
--- a/arch/arm64/kernel/kaslr.c
+++ b/arch/arm64/kernel/kaslr.c
@@ -20,8 +20,8 @@
#include <asm/pgtable.h>
#include <asm/sections.h>
-u64 __read_mostly module_alloc_base;
-u16 __initdata memstart_offset_seed;
+u64 module_alloc_base __read_mostly;
+u16 memstart_offset_seed __initdata;
static __init u64 get_kaslr_seed(void *fdt)
{
--
2.8.1
Powered by blists - more mailing lists