From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux RCU <rcu@vger.kernel.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/2] RCU docs toctree cleanup
Date: Tue, 19 Aug 2025 08:26:18 +0700 [thread overview]
Message-ID: <20250819012620.14606-1-bagasdotme@gmail.com> (raw)
Hi,
As the subject suggests: a small cleanup on RCU documentation toctree index.
The first patch tidying up toctree by not spoiling the full hierarchy
by means of reducing its depth. The second one edits the index title to
reflect nature of the toctree.
Enjoy!
This series is based on kvm-remote.sh wrap patch [1].
[1]: https://lore.kernel.org/linux-doc/20250819004559.11429-1-bagasdotme@gmail.com/
Bagas Sanjaya (2):
Documentation: RCU: Reduce toctree depth
Documentation: RCU: Retitle toctree index
Documentation/RCU/index.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-08-19 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 1:26 Bagas Sanjaya [this message]
2025-08-19 1:26 ` [PATCH 1/2] Documentation: RCU: Reduce toctree depth Bagas Sanjaya
2025-08-19 2:36 ` Paul E. McKenney
2025-08-19 1:26 ` [PATCH 2/2] Documentation: RCU: Retitle toctree index 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=20250819012620.14606-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.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;
as well as URLs for NNTP newsgroup(s).