mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wei Zhang <zhangweilst@gmail.com>
To: corbet@lwn.net, paulmck@kernel.org, rostedt@goodmis.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Wei Zhang <zhangweilst@gmail.com>
Subject: [PATCH] Documentation: RCU: fix section numbers after adding Section 7 in whatisRCU.rst
Date: Tue,  8 Aug 2023 23:58:11 +0800	[thread overview]
Message-ID: <20230808155811.550575-1-zhangweilst@gmail.com> (raw)

Signed-off-by: Wei Zhang <zhangweilst@gmail.com>
---
 Documentation/RCU/whatisRCU.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/RCU/whatisRCU.rst b/Documentation/RCU/whatisRCU.rst
index e488c8e557a9..60ce02475142 100644
--- a/Documentation/RCU/whatisRCU.rst
+++ b/Documentation/RCU/whatisRCU.rst
@@ -59,8 +59,8 @@ experiment with should focus on Section 2.  People who prefer to start
 with example uses should focus on Sections 3 and 4.  People who need to
 understand the RCU implementation should focus on Section 5, then dive
 into the kernel source code.  People who reason best by analogy should
-focus on Section 6.  Section 7 serves as an index to the docbook API
-documentation, and Section 8 is the traditional answer key.
+focus on Section 6 and 7.  Section 8 serves as an index to the docbook
+API documentation, and Section 9 is the traditional answer key.
 
 So, start with the section that makes the most sense to you and your
 preferred method of learning.  If you need to know everything about

base-commit: 14f9643dc90adea074a0ffb7a17d337eafc6a5cc
-- 
2.34.1


             reply	other threads:[~2023-08-08 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08 15:58 Wei Zhang [this message]
2023-08-09  4:54 ` Randy Dunlap
2023-08-11 16:55   ` 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=20230808155811.550575-1-zhangweilst@gmail.com \
    --to=zhangweilst@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@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

all inboxes | Powered by JetHome®