Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] appendix/questions: Add missing NBSPs
Date: Sun, 8 Jan 2017 13:23:53 -0800	[thread overview]
Message-ID: <20170108212353.GR3800@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170108163445.26748-1-sj38.park@gmail.com>

On Mon, Jan 09, 2017 at 01:34:45AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Queued and pushed, thank you, SeongJae!

							Thanx, Paul

> ---
>  appendix/questions/after.tex | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/appendix/questions/after.tex b/appendix/questions/after.tex
> index cbba768dd443..e648667614a4 100644
> --- a/appendix/questions/after.tex
> +++ b/appendix/questions/after.tex
> @@ -184,13 +184,13 @@ SMP code?
>  Simply use SMP primitives as designed.
> 
>  In this example, the easiest fix is to use locking, for example,
> -acquire a lock in the producer before line 10 in
> +acquire a lock in the producer before line~10 in
>  Figure~\ref{fig:app:questions:After Producer Function} and in
>  the consumer before line~13 in
>  Figure~\ref{fig:app:questions:After Consumer Function}.
>  This lock must also be released after line~13 in
>  Figure~\ref{fig:app:questions:After Producer Function} and
> -after line 17 in
> +after line~17 in
>  Figure~\ref{fig:app:questions:After Consumer Function}.
>  These locks cause the code segments in lines~10-13 of
>  Figure~\ref{fig:app:questions:After Producer Function} and in lines~13-17 of
> -- 
> 2.10.0
> 


      reply	other threads:[~2017-01-08 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 16:34 [PATCH] appendix/questions: Add missing NBSPs SeongJae Park
2017-01-08 21:23 ` Paul E. McKenney [this message]

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=20170108212353.GR3800@linux.vnet.ibm.com \
    --to=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