All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junchang Wang <junchangwang@gmail.com>
To: paulmck@linux.ibm.com
Cc: perfbook@vger.kernel.org, Junchang Wang <junchangwang@gmail.com>
Subject: [PATCH 3/3] defer: Fix a typo
Date: Sat, 24 Nov 2018 17:34:54 +0800	[thread overview]
Message-ID: <1543052094-8306-4-git-send-email-junchangwang@gmail.com> (raw)
In-Reply-To: <1543052094-8306-1-git-send-email-junchangwang@gmail.com>

Signed-off-by: Junchang Wang <junchangwang@gmail.com>
---
 defer/hazptr.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/defer/hazptr.tex b/defer/hazptr.tex
index 346146f..09c5f21 100644
--- a/defer/hazptr.tex
+++ b/defer/hazptr.tex
@@ -91,7 +91,7 @@ recorded a hazard pointer for the data element.
 	It might be inefficient in some sense, but the fact is that
 	such restarting is absolutely required for correctness.
 	To see this, consider a hazard-pointer-protected linked list
-	containing elements~A, B, and~C that is subjecte to the
+	containing elements~A, B, and~C that is subjected to the
 	following sequence of events:
 
 	\begin{enumerate}
-- 
2.7.4


  parent reply	other threads:[~2018-11-24  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24  9:34 [PATCH 0/3] Patches for Section Deferred Processing Junchang Wang
2018-11-24  9:34 ` [PATCH 1/3] route_hazptr: Add dependency to hazptr Junchang Wang
2018-11-24  9:34 ` [PATCH 2/3] route_hazptr: Fix a memory leak bug Junchang Wang
2018-11-24  9:34 ` Junchang Wang [this message]
2018-11-24 16:47 ` [PATCH 0/3] Patches for Section Deferred Processing Paul E. McKenney
2018-11-25  2:18   ` Junchang Wang

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=1543052094-8306-4-git-send-email-junchangwang@gmail.com \
    --to=junchangwang@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.