Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <cefc89fc-72cf-7f03-670d-f5649a68b99f@redhat.com>
Date:   Fri, 23 Sep 2022 10:15:04 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.3.0
Subject: Re: linux-next: build failure after merge of the mm tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Andrew Morton <akpm@linux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20220923181245.004d9278@canb.auug.org.au>
Content-Language: en-US
From:   David Hildenbrand <david@redhat.com>
Organization: Red Hat
In-Reply-To: <20220923181245.004d9278@canb.auug.org.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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