From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kernel Tracing <linux-trace-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@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>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Purva Yeshi <purvayeshi550@gmail.com>
Subject: [PATCH 1/2] Documentation: trace: Reduce toctree depth
Date: Tue, 15 Apr 2025 10:46:12 +0700 [thread overview]
Message-ID: <20250415034613.21305-2-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250415034613.21305-1-bagasdotme@gmail.com>
From: Purva Yeshi <purvayeshi550@gmail.com>
Reduce toctree depth from 2 to 1 so that only docs titles are listed
in the toctree. Individual docs' table of contents can be shown on
sidebar by actually visiting the respective docs.
Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Link: https://lore.kernel.org/r/20250318113230.24950-1-purvayeshi550@gmail.com
[Bagas: massage commit message]
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/trace/index.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst
index 2c991dc96ace60..fecc4adf70a830 100644
--- a/Documentation/trace/index.rst
+++ b/Documentation/trace/index.rst
@@ -3,7 +3,7 @@ Linux Tracing Technologies
==========================
.. toctree::
- :maxdepth: 2
+ :maxdepth: 1
ftrace-design
tracepoint-analysis
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-04-15 3:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 3:46 [PATCH 0/2] Table of contents refactoring for tracing docs Bagas Sanjaya
2025-04-15 3:46 ` Bagas Sanjaya [this message]
2025-04-15 3:46 ` [PATCH 2/2] Documentation: trace: Refactor toctree Bagas Sanjaya
2025-04-15 14:06 ` Steven Rostedt
2025-04-16 2:29 ` Bagas Sanjaya
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=20250415034613.21305-2-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--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=purvayeshi550@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).