From: Alan Huang <mmpgouride@gmail.com>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, Alan Huang <mmpgouride@gmail.com>
Subject: [PATCH] advsync: Fix typos
Date: Wed, 7 Jun 2023 11:48:38 +0000 [thread overview]
Message-ID: <20230607114838.4582-1-mmpgouride@gmail.com> (raw)
Signed-off-by: Alan Huang <mmpgouride@gmail.com>
---
advsync/rt.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/advsync/rt.tex b/advsync/rt.tex
index 8e0347b0..c4d9c3c2 100644
--- a/advsync/rt.tex
+++ b/advsync/rt.tex
@@ -1228,7 +1228,7 @@ read-side critical section and both the \co{rt_read_unlock()} and the
This is necessary because non-realtime kernels' reader-writer locking
functions disable preemption across their critical sections, and
there really are reader-writer locking use cases that rely on the fact
-that \co{synchronize_rcu()} will therefore wait for all pre-exiting
+that \co{synchronize_rcu()} will therefore wait for all pre-existing
reader-writer-lock critical sections to complete.
Let this be a lesson to you:
Understanding what your users really need is critically important to
@@ -1745,7 +1745,7 @@ These constraints include:
\end{enumerate}
\QuickQuiz{
- I couldn't help but spot the word ``includes'' before this list.
+ I couldn't help but spot the word ``include'' before this list.
Are there other constraints?
}\QuickQuizAnswer{
Indeed there are, and lots of them.
--
2.34.1
next reply other threads:[~2023-06-07 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 11:48 Alan Huang [this message]
2023-06-08 18:31 ` [PATCH] advsync: Fix typos Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2017-07-15 3:51 [PATCH] Advsync: fix typos Junchang Wang
2017-07-15 5:20 ` Akira Yokosawa
2017-07-15 7: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=20230607114838.4582-1-mmpgouride@gmail.com \
--to=mmpgouride@gmail.com \
--cc=paulmck@kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).