From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752557AbcHLMCn (ORCPT ); Fri, 12 Aug 2016 08:02:43 -0400 Received: from mail-io0-f175.google.com ([209.85.223.175]:36064 "EHLO mail-io0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751574AbcHLMCm (ORCPT ); Fri, 12 Aug 2016 08:02:42 -0400 MIME-Version: 1.0 In-Reply-To: <1470988871-2799-4-git-send-email-jszhang@marvell.com> References: <1470988871-2799-1-git-send-email-jszhang@marvell.com> <1470988871-2799-4-git-send-email-jszhang@marvell.com> From: Ard Biesheuvel Date: Fri, 12 Aug 2016 14:02:40 +0200 Message-ID: Subject: Re: [PATCH v3 3/4] arm64: kaslr: Fix incorrect placement of __initdata and __read_mostly To: Jisheng Zhang Cc: Catalin Marinas , Will Deacon , Lorenzo Pieralisi , Kees Cook , Mark Rutland , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jisheng, On 12 August 2016 at 10:01, Jisheng Zhang wrote: > __initdata and __read_mostly should be placed after the variable name > for the variable to be placed in the intended section. > Why? > Signed-off-by: Jisheng Zhang > --- > 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 > #include > > -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 > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel