From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Junchang Wang <junchangwang@gmail.com>
Cc: dave@stgolabs.net, josh@joshtriplett.org, corbet@lwn.net,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
jiangshanlai@gmail.com, joel@joelfernandes.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] whatisRCU.txt: fix outdated links
Date: Tue, 1 Jan 2019 09:53:22 -0800 [thread overview]
Message-ID: <20190101175322.GV4170@linux.ibm.com> (raw)
In-Reply-To: <1546351400-16389-2-git-send-email-junchangwang@gmail.com>
On Tue, Jan 01, 2019 at 10:03:19PM +0800, Junchang Wang wrote:
> Fix outdated links in whatisRCU.txt.
>
> Signed-off-by: Junchang Wang <junchangwang@gmail.com>
Queued and pushed, thank you!
Thanx, Paul
> ---
> Documentation/RCU/whatisRCU.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt
> index 4a68543..1ace208 100644
> --- a/Documentation/RCU/whatisRCU.txt
> +++ b/Documentation/RCU/whatisRCU.txt
> @@ -302,7 +302,7 @@ rcu_dereference()
> must prohibit. The rcu_dereference_protected() variant takes
> a lockdep expression to indicate which locks must be acquired
> by the caller. If the indicated protection is not provided,
> - a lockdep splat is emitted. See RCU/Design/Requirements.html
> + a lockdep splat is emitted. See RCU/Design/Requirements/Requirements.html
> and the API's code comments for more details and example usage.
>
> The following diagram shows how each API communicates among the
> @@ -560,7 +560,7 @@ presents two such "toy" implementations of RCU, one that is implemented
> in terms of familiar locking primitives, and another that more closely
> resembles "classic" RCU. Both are way too simple for real-world use,
> lacking both functionality and performance. However, they are useful
> -in getting a feel for how RCU works. See kernel/rcupdate.c for a
> +in getting a feel for how RCU works. See kernel/rcu/update.c for a
> production-quality implementation, and see:
>
> http://www.rdrop.com/users/paulmck/RCU
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-01-01 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 14:03 [PATCH 0/2] Documentation/RCU: Update documents Junchang Wang
2019-01-01 14:03 ` [PATCH 1/2] whatisRCU.txt: fix outdated links Junchang Wang
2019-01-01 17:53 ` Paul E. McKenney [this message]
2019-01-01 14:03 ` [PATCH 2/2] torture.txt: update the list of supported torture types Junchang Wang
2019-01-01 17:55 ` Paul E. McKenney
2019-01-02 3:48 ` Junchang Wang
2019-01-02 13:27 ` 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=20190101175322.GV4170@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=junchangwang@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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;
as well as URLs for NNTP newsgroup(s).