All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the jc_docs tree
Date: Thu, 27 Jan 2022 11:22:58 -0700	[thread overview]
Message-ID: <87fsp9rqbh.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220127141518.54dbb9a8@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> 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

  parent reply	other threads:[~2022-01-27 18:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  3:15 linux-next: build warnings after merge of the jc_docs tree Stephen Rothwell
2022-01-27  3:36 ` Stephen Rothwell
2022-01-27 18:22 ` Jonathan Corbet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-12  4:52 Stephen Rothwell
2025-02-12 15:09 ` Jonathan Corbet
2025-02-12 21:05   ` Mauro Carvalho Chehab
2022-10-31  6:05 Stephen Rothwell
2022-10-31  9:02 ` Bagas Sanjaya
2022-10-31 14:27 ` Jonathan Corbet
2021-03-26  7:54 Stephen Rothwell
2021-03-26 19:20 ` Jonathan Corbet
2021-03-10  3:20 Stephen Rothwell
2021-01-19  6:13 Stephen Rothwell
2021-01-19  6:45 ` Stephen Rothwell
2021-01-19  7:16 ` Stephen Rothwell
2021-01-19  9:07 ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsp9rqbh.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.