Skip to contentSkip to conversation

appendix/whymb: Fix a typo, smb_wmb into smp_wmb

PATCH In review SeongJae Park 2 participants 2 messages Feb 17, 2017 – Feb 19, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 appendix/whymb: Fix a typo, smb_wmb into smp_wmb

---
 appendix/whymb/whymemorybarriers.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
appendix/whymb/whymemorybarriers.tex +1 -1
index 9002047a9878..3a22e46beb0c 100644
@@ -2265,7 +2265,7 @@ a write to a given MMIO register affects the value that will next be
 read from {\em some other} MMIO register.
 
 It is not clear why SPARC does not define \co{wmb()} to be
-\co{membar #MemIssue} and \co{smb_wmb()} to be
+\co{membar #MemIssue} and \co{smp_wmb()} to be
 \co{membar #StoreStore},
 as the current definitions seem vulnerable to bugs in some drivers.
 It is quite possible that all the SPARC CPUs that Linux runs on
Signature · 1 line
2.10.0
#1 lore raw
Quoted 1 line · SeongJae Park

Good eyes, applied, thank you!

Thanx, Paul

Quoted 25 lines
---
 appendix/whymb/whymemorybarriers.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
appendix/whymb/whymemorybarriers.tex +1 -1
index 9002047a9878..3a22e46beb0c 100644
@@ -2265,7 +2265,7 @@ a write to a given MMIO register affects the value that will next be
 read from {\em some other} MMIO register.
 
 It is not clear why SPARC does not define \co{wmb()} to be
-\co{membar #MemIssue} and \co{smb_wmb()} to be
+\co{membar #MemIssue} and \co{smp_wmb()} to be
 \co{membar #StoreStore},
 as the current definitions seem vulnerable to bugs in some drivers.
 It is quite possible that all the SPARC CPUs that Linux runs on
Signature · 6 lines
2.10.0

--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html