From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Tracing <linux-trace-kernel@vger.kernel.org>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuai Xue" <xueshuai@linux.alibaba.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Swaraj Gaikwad" <swarajgaikwad1925@gmail.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: [PATCH 1/2] Documentation: tracing: Add toctree entry for PCI tracepoint
Date: Thu, 8 Jan 2026 08:39:55 +0700 [thread overview]
Message-ID: <20260108013956.14351-2-bagasdotme@gmail.com> (raw)
In-Reply-To: <20260108013956.14351-1-bagasdotme@gmail.com>
Sphinx reports missing toctree entry htmldocs warning:
Documentation/trace/events-pci.rst: WARNING: document isn't included in any toctree [toc.not_included]
Fix it by adding the entry for PCI tracepoint documentation.
Fixes: d0eb853678a21b ("Documentation: tracing: Add PCI tracepoint documentation")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Closes: https://lore.kernel.org/linux-next/20260105160000.0368ec8d@canb.auug.org.au/
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/trace/index.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst
index b4a429dc4f7ad6..0a40bfabcf19bf 100644
--- a/Documentation/trace/index.rst
+++ b/Documentation/trace/index.rst
@@ -54,6 +54,7 @@ applications.
events-power
events-nmi
events-msr
+ events-pci
boottime-trace
histogram
histogram-design
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2026-01-08 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 1:39 [PATCH 0/2] PCI tracepoint documentation fixes Bagas Sanjaya
2026-01-08 1:39 ` Bagas Sanjaya [this message]
2026-01-08 4:30 ` [PATCH 1/2] Documentation: tracing: Add toctree entry for PCI tracepoint Randy Dunlap
2026-01-08 1:39 ` [PATCH 2/2] Documentation: tracing: Wrap PCI tracepoint examples Bagas Sanjaya
2026-01-08 4:30 ` Randy Dunlap
2026-01-08 16:06 ` [PATCH 0/2] PCI tracepoint documentation fixes Steven Rostedt
2026-01-08 16:09 ` Bjorn Helgaas
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=20260108013956.14351-2-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=swarajgaikwad1925@gmail.com \
--cc=xueshuai@linux.alibaba.com \
/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