Signed-off-by: Wei Zhang <[email protected]>
---
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
On 8/8/23 08:58, Wei Zhang wrote:
> Signed-off-by: Wei Zhang <[email protected]>
Reviewed-by: Randy Dunlap <[email protected]>
Thanks.
> ---
> 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
--
~Randy
On Tue, Aug 08, 2023 at 09:54:48PM -0700, Randy Dunlap wrote:
>
>
> On 8/8/23 08:58, Wei Zhang wrote:
> > Signed-off-by: Wei Zhang <[email protected]>
>
> Reviewed-by: Randy Dunlap <[email protected]>
> Thanks.
Queued and pushed, thank you both!
Thanx, Paul
> > ---
> > 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
>
> --
> ~Randy