linux-kernel - Re: [PATCH 02/11] arm/mach-keystone: remove legacy _

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <554A4AF6.2060309@oracle.com>
Date:	Wed, 06 May 2015 10:10:14 -0700
From:	santosh shilimkar <santosh.shilimkar@...cle.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Santosh Shilimkar <ssantosh@...nel.org>
CC:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 02/11] arm/mach-keystone: remove legacy __cpuinit sections
 that crept in

On 5/6/2015 3:37 AM, Russell King - ARM Linux wrote:
> On Mon, Apr 27, 2015 at 06:47:51PM -0400, Paul Gortmaker wrote:
>> We removed __cpuinit support (leaving no-op stubs) quite some time
>> ago.  However two crept back in as of commit 5eb3da7246a5b2dfac9f38
>> ("ARM: keystone: Switch over to coherent memory address space")
>>
>> Since we want to clobber the stubs too, get these removed now.
>>
>> Cc: Santosh Shilimkar <santosh.shilimkar@...com>
>
> Santosh's email is now: Santosh Shilimkar <ssantosh@...nel.org>
>
Thanks Russell.


>> Cc: linux-arm-kernel@...ts.infradead.org
>> Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
>> ---
>>   arch/arm/mach-keystone/platsmp.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
Paul, Change is fine by me. I can pick this up for 4.2

Regards,
Santosh
--
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/