linux-kernel - Re: linux-next: build failure after merge of the mm 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]

Message-ID: <cefc89fc-72cf-7f03-670d-f5649a68b99f@redhat.com>
Date:   Fri, 23 Sep 2022 10:15:04 +0200
From:   David Hildenbrand <david@...hat.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the mm tree

On 23.09.22 10:12, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the mm tree, today's linux-next build (htmldocs) failed
> like this:
> 
> Sphinx parallel build error:
> docutils.utils.SystemMessage: /home/sfr/next/next/Documentation/process/coding-style.rst:1213: (SEVERE/4) Title level inconsistent:
> 
> Use WARN_ON_ONCE() rather than WARN() or WARN_ON()
> **************************************************
> 
> Caused by commit
> 
>    13ea678a035b ("coding-style.rst: document BUG() and WARN() rules ("do not crash the kernel")")
> 
> I have reverted that commit for today.

Thanks, an updated patch is already in the works as that issue has been 
raised independently.

-- 
Thanks,

David / dhildenb