[PATCH -perfbook] whymb: Fix typo in variable name

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>From 93f718fcd589225aaf77c5bd804f2ecc07fb6443 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Sun, 5 Dec 2020 13:44:14 +0900
Subject: [PATCH -perfbook] whymb: Fix typo in variable name

It is the variable "b" that CPUs 1 and 2 observe.
This typo was pointed out by Motohiro in his Japanese translation [1].

[1]: https://sites.google.com/site/kandamotohiro/perfbook-d/perfbookappendixc

Cc: Motohiro Kanda <kanda.motohiro@xxxxxxxxx>
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
 appendix/whymb/whymemorybarriers.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/appendix/whymb/whymemorybarriers.tex b/appendix/whymb/whymemorybarriers.tex
index e6c24f6e..d139c4dd 100644
--- a/appendix/whymb/whymemorybarriers.tex
+++ b/appendix/whymb/whymemorybarriers.tex
@@ -1511,7 +1511,7 @@ are both guaranteed to see all assignments by CPU~0 preceding its memory
 barrier on line~2.
 Similarly, CPU~0's memory barrier on line~8 pairs with those of CPUs~1 and 2
 on line~4, so that CPU~0 will not execute the assignment to ``e'' on
-line~9 until after its assignment to ``a'' is visible to both of the
+line~9 until after its assignment to ``b'' is visible to both of the
 other CPUs.
 Therefore, CPU~2's assertion on line~9 is guaranteed \emph{not} to fire.
 
-- 
2.17.1




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux