All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the jc_docs tree
Date: Mon, 7 Dec 2020 18:52:57 +1100	[thread overview]
Message-ID: <20201207185257.1198e407@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

Hi all,

After merging the jc_docs tree, today's linux-next build (htmldocs)
produced this warning:

Documentation/nios2/index.rst:7: WARNING: toctree contains reference to nonexisting document 'nios2/features'

Introduced by commit

  ed13a92d0fde ("docs: archis: add a per-architecture features list")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-12-07  7:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07  7:52 Stephen Rothwell [this message]
2020-12-07  8:56 ` [PATCH] docs: nios2: add missing ReST file Mauro Carvalho Chehab
2020-12-07 21:00   ` Jonathan Corbet
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18  7:28 linux-next: build warning after merge of the jc_docs tree Stephen Rothwell
2023-12-18 14:18 ` Jonathan Corbet
2023-12-19 23:59   ` Randy Dunlap
2023-12-20  0:02     ` Jonathan Corbet
2023-12-20  0:04       ` Randy Dunlap
2021-02-23  5:19 Stephen Rothwell
2021-01-13  4:14 Stephen Rothwell
2021-01-13  4:12 Stephen Rothwell
2021-01-13  4:18 ` Stephen Rothwell
2021-01-13  4:07 Stephen Rothwell
2021-01-13 23:27 ` Jonathan Corbet
2021-01-21  2:07   ` 司延腾
2021-01-21 18:30     ` Jonathan Corbet
2020-11-16  6:03 Stephen Rothwell
2020-12-14 19:51 ` Stephen Rothwell
2020-12-14 20:17   ` Jonathan Corbet

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=20201207185257.1198e407@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    /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.