Skip to contentSkip to conversation

future/tm: Add missing period

PATCH In review SeongJae Park 2 participants 5 messages Dec 26, 2016 – Dec 27, 2016

lore
Share & tools
lore

SeongJae Park

author
#0 lore raw

PATCH 1/4 future/tm: Add missing period

Signed-off-by SeongJae Park <[email protected]>
---
 future/tm.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
future/tm.tex +1 -1
index 04d6c909c299..80aabf4340ed 100644
@@ -641,7 +641,7 @@ lock-based critical sections and from RCU read-side critical sections.
 However, in initial transactional-memory hardware
 implementations~\cite{DaveDice2009ASPLOSRockHTM} an exception within
 a transaction will abort that transaction, which in turn means that
-breakpoints abort all enclosing transactions
+breakpoints abort all enclosing transactions.
 
 So how can transactions be debugged?
Signature · 1 line
2.10.0
author
#1 lore raw

PATCH 2/4 future/htm: Add a missing nbsp

Signed-off-by SeongJae Park <[email protected]>
---
 future/htm.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
future/htm.tex +1 -1
index 625d480b6670..9a1271b4dffe 100644
@@ -388,7 +388,7 @@ have on ease of use.
 	\end{minipage}
 	\vspace{5pt}
 
-	Suppose that the user sets a breakpoint at line 3, which triggers,
+	Suppose that the user sets a breakpoint at line~3, which triggers,
 	aborting the transaction and entering the debugger.
 	Suppose that between the time that the breakpoint triggers
 	and the debugger gets around to stopping all the threads, some
Signature · 1 line
2.10.0
author
#2 lore raw

PATCH 3/4 future: Fix a typo: `item` -> `\item`

In reply to SeongJae Park
Signed-off-by SeongJae Park <[email protected]>
---
 future/htm.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
future/htm.tex +1 -1
index 9a1271b4dffe..ab1002227dfa 100644
@@ -632,7 +632,7 @@ semantics of locking, but loses locking's time-based messaging semantics.
 		\co{MAX_LOOP_TIME}.
 	\item	Locks are used sparingly to access and update global
 		state.
-	item	Locks are granted in strict FIFO order within
+	\item	Locks are granted in strict FIFO order within
 		a given thread priority.
 	\end{enumerate}
Signature · 1 line
2.10.0
author
#3 lore raw

PATCH 4/4 defer/rcu: Fix a section reference typo

In reply to SeongJae Park
Signed-off-by SeongJae Park <[email protected]>
---
 defer/rcu.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
defer/rcu.tex +1 -1
index 121f58d9e609..2ce46e2c0dc3 100644
@@ -8,7 +8,7 @@ All of the mechanisms discussed in the preceding sections
 used one of a number of approaches to defer specific actions
 until they may be carried out safely.
 The reference counters discussed in
-Section~ref{sec:defer:Reference Counting}
+Section~\ref{sec:defer:Reference Counting}
 use explicit counters to defer actions that could disturb readers,
 which results in read-side contention and thus poor scalability.
 The hazard pointers covered by
Signature · 1 line
2.10.0
#4 lore raw

Re: [PATCH 4/4] defer/rcu: Fix a section reference typo

Quoted 1 line · SeongJae Park
Signed-off-by SeongJae Park <[email protected]>

Thank you, queued and pushed all four.

Thanx, Paul

Quoted 20 lines
---
 defer/rcu.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
defer/rcu.tex +1 -1
index 121f58d9e609..2ce46e2c0dc3 100644
@@ -8,7 +8,7 @@ All of the mechanisms discussed in the preceding sections
 used one of a number of approaches to defer specific actions
 until they may be carried out safely.
 The reference counters discussed in
-Section~ref{sec:defer:Reference Counting}
+Section~\ref{sec:defer:Reference Counting}
 use explicit counters to defer actions that could disturb readers,
 which results in read-side contention and thus poor scalability.
 The hazard pointers covered by
Signature · 1 line
2.10.0