public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Steven Rostedt <rostedt@goodmis.org>,
	Jonathan Corbet <corbet@lwn.net>
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 ftrace tree
Date: Sat, 15 Jan 2022 10:55:44 +0100	[thread overview]
Message-ID: <92e4dd91-8d28-b059-ebd4-3c4e027662ad@kernel.org> (raw)
In-Reply-To: <20220115152812.32d3ba5a@canb.auug.org.au>

Hi Stephen

On 1/15/22 05:28, Stephen Rothwell wrote:
> 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")
> 

The Documentation/tools/$tools/ is a new directory to store man pages of the
$tools. The idea seems to be to create a '"book" within the larger documentation 
collection'.

I moved the documentation to that directory following Corbet's suggestion [1], 
but the "book" was not yet created. I think it deserves the hands of a more 
expert person in Docs.

Thoughts?

[1] https://lore.kernel.org/lkml/5796a3d5-ae98-9d28-138f-981a06dab34b@kernel.org/

-- Daniel

  reply	other threads:[~2022-01-15 10:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15  4:28 linux-next: build warnings after merge of the ftrace tree Stephen Rothwell
2022-01-15  9:55 ` Daniel Bristot de Oliveira [this message]
  -- 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=92e4dd91-8d28-b059-ebd4-3c4e027662ad@kernel.org \
    --to=bristot@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox