From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 40747C433FE for ; Thu, 27 Jan 2022 18:22:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244934AbiA0SW3 (ORCPT ); Thu, 27 Jan 2022 13:22:29 -0500 Received: from ms.lwn.net ([45.79.88.28]:52002 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231634AbiA0SW1 (ORCPT ); Thu, 27 Jan 2022 13:22:27 -0500 Received: from localhost (unknown [IPv6:2601:281:8300:104d::5f6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 5953E37C; Thu, 27 Jan 2022 18:22:27 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 5953E37C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1643307747; bh=XfL2rMwB81zqw0aoEZ5tU0tqjPVDfzEabS+h9K9qU/E=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=mIcmoZxWDfNULtRHqDbvsxc0oPqCU0Q737OqMOGlYsarY2WD5TfzUixpnRTC3GwGV tVCGrUdLbC1wiX2rvluCRr4kBSbS5Bo/bBe+q2BICQz6yT1efflCrVUiwnL/LMYZrn vGYL1QJurfB2Oe1MzsOAXmDKb4WQllG+XaePTg8yUuZrBZE+UeabHzJbXUZUcSPjjr XSXG3EabEdgSwZ4Q2hnKaG3pAEMWy7LF7EdVhvVRIlLYvINk7dUO4EuBCHoS7KNHCZ EWqfo7SK8DDn/+hbAlGyJ8vE4/1XS0p0vJxM9BegJp1HpVyGA80sMCDM9cb5RaczY9 CDXZEzcCkCypw== From: Jonathan Corbet To: Stephen Rothwell Cc: Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build warnings after merge of the jc_docs tree In-Reply-To: <20220127141518.54dbb9a8@canb.auug.org.au> References: <20220127141518.54dbb9a8@canb.auug.org.au> Date: Thu, 27 Jan 2022 11:22:58 -0700 Message-ID: <87fsp9rqbh.fsf@meer.lwn.net> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stephen Rothwell writes: > Hi all, > > After merging the jc_docs tree, today's linux-next build (htmldocs) > produced these warnings: > > Documentation/tools/index.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent. > Documentation/tools/index.rst: WARNING: document isn't included in any toctree So this is bizarre...somehow the change to Documentation/index.rst that brings all this stuff in didn't survive the cherry-pick that brought that change into docs-next. No idea how that came to be. The other warning, instead, was just me being dumb about inserting the SPDX lines and forgetting the necessary blank line. Fixed (forcing a rebase of docs-next), apologies for the noise, jon