linux-kernel - Re: linux-next: build warning after merge of the akpm-current tree

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]

Date:   Thu, 3 Feb 2022 15:21:08 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Andrew Morton <akpm@...ux-foundation.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Huang Ying <ying.huang@...el.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the akpm-current tree



On 2/3/22 15:06, Andrew Morton wrote:
> On Wed, 2 Feb 2022 14:54:37 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
>> Hi all,
>>
>> After merging the akpm-current tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> Documentation/admin-guide/sysctl/kernel.rst:603: WARNING: Malformed table.
>> Text in column margin in table line 2.
>>
>> = =================================
>> 0x0 NUMA_BALANCING_DISABLED
>> 0x1 NUMA_BALANCING_NORMAL
>> 0x2 NUMA_BALANCING_MEMORY_TIERING
>> = =================================
>>
>> Introduced by commit
>>
>>   49ec6eb41c49 ("NUMA balancing: optimize page placement for memory tiering system")
> 
> I assume this fixes?  (With gratuitous grammar fixes)
> 

Looks good.

 --- a/Documentation/admin-guide/sysctl/kernel.rst~numa-balancing-optimize-page-placement-for-memory-tiering-system-fix
> +++ a/Documentation/admin-guide/sysctl/kernel.rst
> @@ -595,14 +595,14 @@ Documentation/admin-guide/kernel-paramet
>  numa_balancing
>  ==============
>  
> -Enables/disables and configure automatic page fault based NUMA memory
> -balancing.  Memory is moved automatically to nodes that access it
> -often.  The value to set can be the result to OR the following,
> +Enables/disables and configures automatic page fault based NUMA memory
> +balancing.  Memory is moved automatically to nodes that access it often. 
> +The value to set can be the result of ORing the following,

except for that ending comma...

>  
>  = =================================
> -0x0 NUMA_BALANCING_DISABLED
> -0x1 NUMA_BALANCING_NORMAL
> -0x2 NUMA_BALANCING_MEMORY_TIERING
> +0 NUMA_BALANCING_DISABLED
> +1 NUMA_BALANCING_NORMAL
> +2 NUMA_BALANCING_MEMORY_TIERING
>  = =================================
>  
>  Or NUMA_BALANCING_NORMAL to optimize page placement among different
> _
> 

Thanks.
-- 
~Randy