From: Purva Yeshi <purvayeshi550@gmail.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Purva Yeshi <purvayeshi550@gmail.com>
Subject: [PATCH v4 1/2] docs: tracing: Reduce maxdepth in index.rst for clarity
Date: Tue, 18 Mar 2025 17:02:29 +0530 [thread overview]
Message-ID: <20250318113230.24950-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>
---
V1 - https://lore.kernel.org/all/20250204133616.27694-1-purvayeshi550@gmail.com/
V2 - https://lore.kernel.org/lkml/20250206141453.139613-1-purvayeshi550@gmail.com/
V3 - https://lore.kernel.org/all/20250312124717.7208-1-purvayeshi550@gmail.com/
V4 - Reorder patches to apply the 'maxdepth' change first, then refactor
the index documentation to avoid introducing maxdepth: 2 only to modify
it in the next patch.
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 2c991dc96..fecc4adf7 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
--
2.34.1
next reply other threads:[~2025-03-18 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 11:32 Purva Yeshi [this message]
2025-03-18 11:32 ` [PATCH v4 2/2] docs: tracing: Refactor index.rst for clarity Purva Yeshi
2025-03-18 14:23 ` Bagas Sanjaya
2025-03-21 14:25 ` Steven Rostedt
2025-04-08 0:55 ` Bagas Sanjaya
2025-03-18 14:22 ` [PATCH v4 1/2] docs: tracing: Reduce maxdepth in " 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=20250318113230.24950-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 \
/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