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 1/2] toolsoftrade: Add a missed unbreakable space for line number
Date: Sun, 4 Feb 2018 17:32:20 -0800	[thread overview]
Message-ID: <20180205013220.GT3617@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180204221135.1001-1-sj38.park@gmail.com>

On Mon, Feb 05, 2018 at 07:11:34AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Good catches, both applied, thank you!

							Thanx, Paul

> ---
>  toolsoftrade/toolsoftrade.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
> index e7a922b..ac25855 100644
> --- a/toolsoftrade/toolsoftrade.tex
> +++ b/toolsoftrade/toolsoftrade.tex
> @@ -272,7 +272,7 @@ If the process ID is instead $-1$, this indicates that the \co{wait()}
>  primitive was unable to wait on a child.
>  If so, line~9 checks for the \co{ECHILD} errno, which indicates that there
>  are no more child processes, so that line~10 exits the loop.
> -Otherwise, lines~11 and 12 print an error and exit.
> +Otherwise, lines~11 and~12 print an error and exit.
> 
>  \QuickQuiz{}
>  	Why does this \co{wait()} primitive need to be so complicated?
> -- 
> 2.10.0
> 


      parent reply	other threads:[~2018-02-05  1:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 22:11 [PATCH 1/2] toolsoftrade: Add a missed unbreakable space for line number SeongJae Park
2018-02-04 22:11 ` [PATCH 2/2] toolsoftrade: Use `\path{}` for filename SeongJae Park
2018-02-05  1:32 ` 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=20180205013220.GT3617@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