From: Purva Yeshi <purvayeshi550@gmail.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, corbet@lwn.net
Cc: skhan@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Purva Yeshi <purvayeshi550@gmail.com>
Subject: [PATCH] docs: tracing: Reduce maxdepth in index documentation
Date: Mon, 17 Feb 2025 16:51:09 +0530 [thread overview]
Message-ID: <20250217112109.7734-1-purvayeshi550@gmail.com> (raw)
Reduce :maxdepth: from 2 to 1 in index.rst to simplify the table of
contents, showing only top-level document titles for better readability.
Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
---
Documentation/trace/index.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst
index 6b268194f..5ddd47ee7 100644
--- a/Documentation/trace/index.rst
+++ b/Documentation/trace/index.rst
@@ -14,7 +14,7 @@ This section provides an overview of Linux tracing mechanisms
and debugging approaches.
.. toctree::
- :maxdepth: 2
+ :maxdepth: 1
debugging
tracepoints
@@ -28,7 +28,7 @@ The following are the primary tracing frameworks integrated into
the Linux kernel.
.. toctree::
- :maxdepth: 2
+ :maxdepth: 1
ftrace
ftrace-design
@@ -47,7 +47,7 @@ A detailed explanation of event tracing mechanisms and their
applications.
.. toctree::
- :maxdepth: 2
+ :maxdepth: 1
events
events-kmem
@@ -65,7 +65,7 @@ This section covers tracing features that monitor hardware
interactions and system performance.
.. toctree::
- :maxdepth: 2
+ :maxdepth: 1
intel_th
stm
@@ -85,7 +85,7 @@ These tools allow tracing user-space applications and
interactions.
.. toctree::
- :maxdepth: 2
+ :maxdepth: 1
user_events
--
2.34.1
next reply other threads:[~2025-02-17 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:21 Purva Yeshi [this message]
2025-02-20 3:09 ` Bagas Sanjaya
2025-03-11 12:03 ` Purva Yeshi
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=20250217112109.7734-1-purvayeshi550@gmail.com \
--to=purvayeshi550@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=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®