Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] defer/refcnt: Another typo fix
Date: Mon, 11 Jul 2016 08:59:17 -0700	[thread overview]
Message-ID: <20160711155917.GL4650@linux.vnet.ibm.com> (raw)
In-Reply-To: <75cf85b4-97e8-1425-911b-4f4713aff57e@gmail.com>

On Tue, Jul 12, 2016 at 12:36:29AM +0900, Akira Yokosawa wrote:
> From ae44b15b34f4cba077d0c49e7416f66681895a3d Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Tue, 12 Jul 2016 00:33:08 +0900
> Subject: [PATCH] defer/refcnt: Another typo fix
> 
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>

Good eyes!  Applied and pushed both, thank you!

							Thanx, Paul

> ---
>  defer/refcnt.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/defer/refcnt.tex b/defer/refcnt.tex
> index 8dfa8fe..76ebf4d 100644
> --- a/defer/refcnt.tex
> +++ b/defer/refcnt.tex
> @@ -267,7 +267,7 @@ Figure~\ref{fig:defer:Pre-BSD Packet Routing List}:
>  The problem is that the reference count is located in the object
>  to be protected, but that means that there is no protection during
> -the instant in time when the reference count itself if being acquired!
> +the instant in time when the reference count itself is being acquired!
>  This is the reference-counting counterpart of a locking issue noted
>  by Gamsa et al.~\cite{Gamsa99}.
>  One could imagine using a global lock or reference count to protect
> -- 
> 1.9.1
> 


      reply	other threads:[~2016-07-11 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 15:36 [PATCH] defer/refcnt: Another typo fix Akira Yokosawa
2016-07-11 15:59 ` 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=20160711155917.GL4650@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akiyks@gmail.com \
    --cc=perfbook@vger.kernel.org \
    /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