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] [day] [month] [year] [list]
Message-ID: <847b9b8a-d9d5-3ee9-41f3-1171a4f73434@huawei.com>
Date:   Fri, 26 May 2023 19:40:54 +0800
From:   Kefeng Wang <wangkefeng.wang@...wei.com>
To:     kernel test robot <lkp@...el.com>, Mike Rapoport <rppt@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
CC:     <oe-kbuild-all@...ts.linux.dev>,
        Linux Memory Management List <linux-mm@...ck.org>,
        <linux-kernel@...r.kernel.org>, <tsahu@...ux.ibm.com>,
        <anshuman.khandual@....com>, <ssawgyw@...il.com>
Subject: Re: [PATCH -next] memblock: unify memblock dump and debugfs show



On 2023/5/26 19:09, kernel test robot wrote:
> Hi Kefeng,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on next-20230525]
> 
Thank, I will drop __initdata_memblock .

> 
> 
> vim +1910 mm/memblock.c
> 
>    1909	
>> 1910	static const char * const flagname[] __initdata_memblock = {
>    1911		[ilog2(MEMBLOCK_HOTPLUG)]		= "HOTPLUG",
>    1912		[ilog2(MEMBLOCK_MIRROR)]		= "MIRROR",
>    1913		[ilog2(MEMBLOCK_NOMAP)]			= "NOMAP",
>    1914		[ilog2(MEMBLOCK_DRIVER_MANAGED)]	= "DRV_MNG",
>    1915		[ilog2(MEMBLOCK_MAX_UNKNOWN)]		= "UNKNOWN",
>    1916	};
>    1917	
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ