All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the ftrace tree
Date: Sat, 15 Jan 2022 15:28:12 +1100	[thread overview]
Message-ID: <20220115152812.32d3ba5a@canb.auug.org.au> (raw)

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

Hi all,

After merging the ftrace tree, today's linux-next build (htmldoc)
produced these warnings:

Documentation/tools/rtla/rtla-osnoise-hist.rst: WARNING: document isn't included in any toctree
Documentation/tools/rtla/rtla-osnoise-top.rst: WARNING: document isn't included in any toctree
Documentation/tools/rtla/rtla-timerlat.rst: WARNING: document isn't included in any toctree
Documentation/tools/rtla/rtla-timerlat-hist.rst: WARNING: document isn't included in any toctree
Documentation/tools/rtla/rtla-timerlat-top.rst: WARNING: document isn't included in any toctree

Introduced by commits

  b1be48307de4 ("rtla: Add rtla osnoise top documentation")
  e7041c6b3c12 ("rtla: Add rtla osnoise hist documentation")
  29380d4055e5 ("rtla: Add rtla timerlat documentation")
  df337d014b57 ("rtla: Add rtla timerlat top documentation")
  5dce5904e3b9 ("rtla: Add rtla timerlat hist documentation")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-01-15  4:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15  4:28 Stephen Rothwell [this message]
2022-01-15  9:55 ` linux-next: build warnings after merge of the ftrace tree Daniel Bristot de Oliveira
  -- strict thread matches above, loose matches on Subject: below --
2023-01-30  5:51 Stephen Rothwell
2023-01-30 18:51 ` Steven Rostedt
2023-01-31  8:24   ` Bagas Sanjaya
2016-07-04  5:42 Stephen Rothwell
2016-07-05 19:29 ` Steven Rostedt

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=20220115152812.32d3ba5a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bristot@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rostedt@goodmis.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.