Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/3] Employ new scheme for code snippets (cont.)
Date: Sun, 25 Nov 2018 14:39:01 -0800	[thread overview]
Message-ID: <20181125223901.GF4170@linux.ibm.com> (raw)
In-Reply-To: <e91f0cf9-4710-1ef1-705c-ad4deeaf1ccb@gmail.com>

On Mon, Nov 26, 2018 at 07:07:12AM +0900, Akira Yokosawa wrote:
> On 2018/11/25 09:01:59 -0800, Paul E. McKenney wrote:
> > On Sun, Nov 25, 2018 at 11:44:41PM +0900, Akira Yokosawa wrote:
> >> >From 4ebe85f38ed5f0e003847854b64bc8773bec8ebb Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiyks@gmail.com>
> >> Date: Sun, 25 Nov 2018 23:30:16 +0900
> >> Subject: [PATCH 0/3] Employ new scheme (cont.)
> >>
> >> Hi Paul,
> >>
> >> This is a set of patches to further apply the new scheme for snippets in
> >> chapters "owned" and "defer". Further updates in "defer" will be submitted
> >> shortly.
> > 
> > Good stuff, applied, thank you!
> > 
> > I also fixed a filename typo (my fault, not yours)
> 
> Well, it was *my* typo in 2/3 of the patch set. (There was no mention
> of the file name.)

True enough.  My typo was instead leaving it out completely.

> Thank you for catching it!

And you!  ;-)

							Thanx, Paul

> Akira
> 
> >                                                    and expanded a bit
> > on the topic of mechanical reference counting.
> > 
> > 							Thanx, Paul
> > 
> >>         Thanks, Akira
> >> --
> >> Akira Yokosawa (3):
> >>   owned: Employ new snippet scheme
> >>   defer: Employ new snippet scheme for route_seq.c
> >>   defer: Employ new scheme for snippets of route_refcnt.c
> >>
> >>  CodeSamples/defer/route_refcnt.c |  67 +++++++++--------
> >>  CodeSamples/defer/route_seq.c    |  42 +++++------
> >>  defer/defer.tex                  |  76 ++++----------------
> >>  defer/refcnt.tex                 | 152 +++++++++------------------------------
> >>  owned/owned.tex                  |  19 ++---
> >>  5 files changed, 115 insertions(+), 241 deletions(-)
> >>
> >> -- 
> >> 2.7.4
> >>
> > 
> 


      reply	other threads:[~2018-11-26  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 14:44 [PATCH 0/3] Employ new scheme for code snippets (cont.) Akira Yokosawa
2018-11-25 14:46 ` [PATCH 1/3] owned: Employ new snippet scheme Akira Yokosawa
2018-11-25 14:48   ` [PATCH 2/3] defer: Employ new snippet scheme for route_seq.c Akira Yokosawa
2018-11-25 14:50   ` [PATCH 3/3] defer: Employ new scheme for snippets of route_refcnt.c Akira Yokosawa
2018-11-25 17:01 ` [PATCH 0/3] Employ new scheme for code snippets (cont.) Paul E. McKenney
2018-11-25 22:07   ` Akira Yokosawa
2018-11-25 22:39     ` 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=20181125223901.GF4170@linux.ibm.com \
    --to=paulmck@linux.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