All of lore.kernel.org
 help / color / mirror / Atom feed
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 2/5] defer/rcupai: Fix a typo: _pointer()() -> _pointer()
Date: Fri, 26 Apr 2019 09:57:01 +0900	[thread overview]
Message-ID: <20190426005704.10952-3-sj38.park@gmail.com> (raw)
In-Reply-To: <20190426005704.10952-1-sj38.park@gmail.com>

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 defer/rcuapi.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/defer/rcuapi.tex b/defer/rcuapi.tex
index 93b9767..6e014e0 100644
--- a/defer/rcuapi.tex
+++ b/defer/rcuapi.tex
@@ -570,7 +570,7 @@ Again, simply loading these pointers using C-language accesses
 could result in seeing pre-initialization garbage in the pointed-to data.
 However, if the pointer is merely to be tested and not dereferenced,
 this protection is not needed.
-In this case, \co{rcu_access_pointer()()} may be used.
+In this case, \co{rcu_access_pointer()} may be used.
 Normally, however, protection is required, and so the
 \co{rcu_dereference()} primitive ensures that subsequent code
 dereferencing the pointer will see the effects of initialization code
-- 
2.10.0


  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 ` SeongJae Park [this message]
2019-04-26  0:57 ` [PATCH 3/5] defer/rcuapi: Consistently use dashes for 'RCU-protected' and 'update-side' SeongJae Park
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-3-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.