From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@linux.ibm.com
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 3/5] defer/rcuapi: Consistently use dashes for 'RCU-protected' and 'update-side'
Date: Fri, 26 Apr 2019 09:57:02 +0900 [thread overview]
Message-ID: <20190426005704.10952-4-sj38.park@gmail.com> (raw)
In-Reply-To: <20190426005704.10952-1-sj38.park@gmail.com>
Only one sentence is not placing a 'dash' between two words: 'RCU
protected' and 'update side'. This commit adds dashes for better
consistency.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
defer/rcuapi.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/defer/rcuapi.tex b/defer/rcuapi.tex
index 6e014e0..72aa10c 100644
--- a/defer/rcuapi.tex
+++ b/defer/rcuapi.tex
@@ -578,8 +578,8 @@ prior to the corresponding \co{rcu_assign_pointer()}, even on Alpha CPUs.
On non-Alpha CPUs, \co{rcu_dereference()} documents which pointer
dereferences require RCU protection.
-Another situation where protection is not required is when update side code
-accesses the RCU protected pointer while holding the update-side lock.
+Another situation where protection is not required is when update-side code
+accesses the RCU-protected pointer while holding the update-side lock.
The \co{rcu_dereference_protected()} API member is provided for this
situation.
Its first parameter is the RCU-protected pointer, and the second
--
2.10.0
next prev parent reply other threads:[~2019-04-26 0:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 0:56 [PATCH] memorder: Fix two trivial typos SeongJae Park
2019-04-26 0:57 ` [PATCH 1/5] toolsoftrade: Polish an ambiguous sentence SeongJae Park
2019-04-26 14:17 ` Paul E. McKenney
2019-04-26 0:57 ` [PATCH 2/5] defer/rcupai: Fix a typo: _pointer()() -> _pointer() SeongJae Park
2019-04-26 0:57 ` SeongJae Park [this message]
2019-04-26 0:57 ` [PATCH 4/5] defer: Fix a typo: processof -> process of SeongJae Park
2019-04-26 0:57 ` [PATCH 5/5] defer: Use 'Go' instead of 'golang' SeongJae Park
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=20190426005704.10952-4-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=perfbook@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.