linux-kernel - Re: [PATCH 01/11] arm64: numa: Remove the unused parent

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]

Date:   Fri, 4 Aug 2017 23:28:36 +0800
From:   Dou Liyang <douly.fnst@...fujitsu.com>
To:     Will Deacon <will.deacon@....com>
CC:     <linux-kernel@...r.kernel.org>, <mpe@...erman.id.au>,
        <linux-arm-kernel@...ts.infradead.org>, <catalin.marinas@....com>
Subject: Re: [PATCH 01/11] arm64: numa: Remove the unused parent_node() macro

Hi will,

At 08/04/2017 09:30 PM, Will Deacon wrote:
> On Wed, Jul 26, 2017 at 09:34:26PM +0800, Dou Liyang wrote:
>> Commit a7be6e5a7f8d ("mm: drop useless local parameters of
>> __register_one_node()") removes the last user of parent_node().
>>
>> The parent_node() macro in ARM64 platform is unnecessary.
>>
>> Remove it for cleanup.
>>
>> Reported-by: Michael Ellerman <mpe@...erman.id.au>
>> Signed-off-by: Dou Liyang <douly.fnst@...fujitsu.com>
>> Cc: Michael Ellerman <mpe@...erman.id.au>
>> Cc: Will Deacon <will.deacon@....com>
>> Cc: linux-arm-kernel@...ts.infradead.org
>> ---
>>  arch/arm64/include/asm/numa.h | 3 ---
>>  1 file changed, 3 deletions(-)
>>
>> diff --git a/arch/arm64/include/asm/numa.h b/arch/arm64/include/asm/numa.h
>> index bf466d1..ef7b238 100644
>> --- a/arch/arm64/include/asm/numa.h
>> +++ b/arch/arm64/include/asm/numa.h
>> @@ -7,9 +7,6 @@
>>
>>  #define NR_NODE_MEMBLKS		(MAX_NUMNODES * 2)
>>
>> -/* currently, arm64 implements flat NUMA topology */
>> -#define parent_node(node)	(node)
>> -
>
> Acked-by: Will Deacon <will.deacon@....com>
>
> Where you intending for this to go via the arm64 tree?
>

I intend for this to go to upstream tree. shall we?

Thanks

	dou.


> Will
>
>
>