netdev - Re: linux-next: build warnings after merge of the net-next 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:   Fri, 19 Feb 2021 16:57:44 +0200
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     David Miller <davem@...emloft.net>,
        Networking <netdev@...r.kernel.org>,
        Alexei Starovoitov <ast@...nel.org>,
        Brendan Jackman <jackmanb@...gle.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the net-next tree

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> Hi all,
>
> On Fri, 19 Feb 2021 07:52:56 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>
>> After merging the net-next tree, today's linux-next build (htmldocs)
>> produced these warnings:
>> 
>> Documentation/networking/filter.rst:1053: WARNING: Inline emphasis start-string without end-string.
>> Documentation/networking/filter.rst:1053: WARNING: Inline emphasis start-string without end-string.
>> Documentation/networking/filter.rst:1053: WARNING: Inline emphasis start-string without end-string.
>> Documentation/networking/filter.rst:1053: WARNING: Inline emphasis start-string without end-string.
>> 
>> Introduced by commit
>> 
>>   91c960b00566 ("bpf: Rename BPF_XADD and prepare to encode other atomics in .imm")
>> 
>> Sorry that I missed these earlier.
>
> These have been fixed in the net-next tree, actually.  I was fooled
> because an earlier part of the net-next tree has been included in the
> wireless-drivers (not -next) tree today so these warnings popped up
> earlier, but are gone one the rest of the net-next tree is merged.
>
> Sorry for the noise.

Argh, sorry about that Stephen. I was preparing wireless-drivers for
followup fixes sent during the merge window, but didn't realise that it
will mess up your tree building. I need to avoid this in the future and
wireless-drivers should only follow the net tree.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches