Linux RCU subsystem development
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
	rostedt@goodmis.org, Bagas Sanjaya <bagasdotme@gmail.com>,
	"Paul E . McKenney" <paulmck@kernel.org>
Subject: [PATCH v2 5/8] Documentation: RCU: Reduce toctree depth
Date: Thu, 18 Sep 2025 03:14:27 -0700	[thread overview]
Message-ID: <20250918101430.2592294-5-paulmck@kernel.org> (raw)
In-Reply-To: <921eb978-5f39-4480-bcf6-c735f859c694@paulmck-laptop>

From: Bagas Sanjaya <bagasdotme@gmail.com>

toctree index for RCU currently has maximum depth of 3. Since no docs
currently use more than 3 section heading levels, this effectively spills
the entire docs hierarchy.

Tidy up by reducing toctree depth to 2 (only showing docs title and
second-level sections).

Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
 Documentation/RCU/index.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/RCU/index.rst b/Documentation/RCU/index.rst
index 84a79903f6a883..e1be5b3c2c6773 100644
--- a/Documentation/RCU/index.rst
+++ b/Documentation/RCU/index.rst
@@ -7,7 +7,7 @@ RCU concepts
 ============
 
 .. toctree::
-   :maxdepth: 3
+   :maxdepth: 2
 
    checklist
    lockdep
-- 
2.40.1


  parent reply	other threads:[~2025-09-18 10:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 23:59 [PATCH 0/3] rcu: Documentation updates for v6.18 Paul E. McKenney
2025-08-16  0:00 ` [PATCH 1/3] doc: Update whatisRCU.rst for recent RCU API additions Paul E. McKenney
2025-08-16  3:54   ` Bagas Sanjaya
2025-08-16  4:54     ` Paul E. McKenney
2025-08-16  5:38       ` Bagas Sanjaya
2025-08-16 11:28         ` Paul E. McKenney
2025-08-16  0:00 ` [PATCH 2/3] doc: Add RCU guards to checklist.rst Paul E. McKenney
2025-08-16  0:00 ` [PATCH 3/3] rcu: docs: Requirements.rst: Abide by conventions of kernel documentation Paul E. McKenney
2025-08-16  1:30   ` Akira Yokosawa
2025-08-16  2:02     ` Paul E. McKenney
2025-09-18 10:14 ` [PATCH 0/3] rcu: Documentation updates for v6.18 Paul E. McKenney
2025-09-18 10:14   ` [PATCH v2 1/8] doc: Update whatisRCU.rst for recent RCU API additions Paul E. McKenney
2025-09-18 10:14   ` [PATCH v2 2/8] doc: Add RCU guards to checklist.rst Paul E. McKenney
2025-09-18 10:14   ` [PATCH v2 3/8] rcu: docs: Requirements.rst: Abide by conventions of kernel documentation Paul E. McKenney
2025-09-18 10:14   ` [PATCH v2 4/8] Documentation: RCU: Wrap kvm-remote.sh rerun snippet in literal code block Paul E. McKenney
2025-09-18 10:14   ` Paul E. McKenney [this message]
2025-09-18 10:14   ` [PATCH v2 6/8] Documentation: RCU: Retitle toctree index Paul E. McKenney
2025-09-18 10:14   ` [PATCH v2 7/8] doc: Fix typo in RCU's torture.rst documentation Paul E. McKenney
2025-09-18 10:14   ` [PATCH v2 8/8] docs: rcu: Replace multiple dead OLS links in RTFP.txt Paul E. McKenney

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=20250918101430.2592294-5-paulmck@kernel.org \
    --to=paulmck@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rcu@vger.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