From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: sj38.park@gmail.com, perfbook@vger.kernel.org
Subject: [PATCH] advsync: Another fix to use latex reference feature consistently
Date: Sat, 9 Apr 2016 12:54:47 +0900 [thread overview]
Message-ID: <57087D07.6030207@gmail.com> (raw)
Hello,
This is the first time I submit a patch.
I'm not sure the format below is acceptable or not, but just trying.
If there is any issue, please advise me.
Regards,
Akira Yokosawa <akiyks@gmail.com>
-- >8 --
Subject: [PATCH] advsync: Another fix to use latex reference feature consistently
In commit 91bde6aa87c2884f19d2a83534236cdbb319d625, SeongJae Park
has made changes to enforce latex reference feature to the references
in the `Advanced Synchronization` chapter. However one of section
name direct citations is left unchanged in the commit.
This commit fixes the remaining one.
Signed-off-by: Akira Yokosawa <akiysw@gmail.com>
---
advsync/memorybarriers.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
index 12771ec..e527def 100644
--- a/advsync/memorybarriers.tex
+++ b/advsync/memorybarriers.tex
@@ -1508,7 +1508,7 @@ Read memory barriers imply data dependency barriers, and so can substitute
for them.
$\dagger$ Note that read barriers should normally be paired with write barriers;
-see the ``SMP barrier pairing'' subsection.
+see Secton~\ref{sec:advsync:SMP Barrier Pairing}.
\paragraph{General Memory Barriers}
--
1.9.1
next reply other threads:[~2016-04-09 3:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 3:54 Akira Yokosawa [this message]
2016-04-09 5:46 ` [PATCH] advsync: Another fix to use latex reference feature consistently SeongJae Park
2016-04-12 16:00 ` Paul E. McKenney
2016-04-12 22:15 ` Akira Yokosawa
2016-04-12 22:36 ` 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=57087D07.6030207@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.com \
/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