[PATCH 1/4] future/tm: Add missing period

[PATCH 1/4] future/tm: Add missing period

[SeongJae Park]

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 future/tm.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/future/tm.tex b/future/tm.tex
index 04d6c909c299..80aabf4340ed 100644
--- a/future/tm.tex
+++ b/future/tm.tex
@@ -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?

-- 
2.10.0

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

[SeongJae Park]

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 future/htm.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/future/htm.tex b/future/htm.tex
index 625d480b6670..9a1271b4dffe 100644
--- a/future/htm.tex
+++ b/future/htm.tex
@@ -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
-- 
2.10.0

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

[SeongJae Park]

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 future/htm.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/future/htm.tex b/future/htm.tex
index 9a1271b4dffe..ab1002227dfa 100644
--- a/future/htm.tex
+++ b/future/htm.tex
@@ -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}

-- 
2.10.0

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

[SeongJae Park]

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 defer/rcu.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/defer/rcu.tex b/defer/rcu.tex
index 121f58d9e609..2ce46e2c0dc3 100644
--- a/defer/rcu.tex
+++ b/defer/rcu.tex
@@ -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
-- 
2.10.0

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

[Paul E. McKenney]

On Tue, Dec 27, 2016 at 04:43:14AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Thank you, queued and pushed all four.

							Thanx, Paul

> ---
>  defer/rcu.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/defer/rcu.tex b/defer/rcu.tex
> index 121f58d9e609..2ce46e2c0dc3 100644
> --- a/defer/rcu.tex
> +++ b/defer/rcu.tex
> @@ -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
> -- 
> 2.10.0
>