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/7] count, toolsoftrade: Employ new code-snippet scheme (cont.)
Date: Fri, 26 Oct 2018 13:58:45 -0700	[thread overview]
Message-ID: <20181026205845.GZ4170@linux.ibm.com> (raw)
In-Reply-To: <5342e889-ee54-cb5d-c498-b887bcb79863@gmail.com>

On Sat, Oct 27, 2018 at 12:35:10AM +0900, Akira Yokosawa wrote:
> On 2018/10/27 00:22:37 +0900, Akira Yokosawa wrote:
> > Hi Paul,
> > 
> > This is a set of simple conversions of code snippets to the new scheme
> > in count and toolsoftrade.  There is no change in the code under CodeSamples,
> > but there are a few visual changes in the pdf output which reflect the
> > actual code samples.
> 
> I forgot to mention that Patch #3 contains minor changes in the code to
> reduce width of code snippets.
> 
>         Thanks, Akira
> 
> > 
> > Patch #7 fixes an unintended change in indent width made in the previous
> > patch set.
> > 
> >         Thanks, Akira

I applied and pushed this series, thank you!

							Thanx, Paul

> > --
> > Akira Yokosawa (7):
> >   count: Employ new scheme for inline code snippets
> >   toolsoftrade: Use 'VerbatimU' for inline snippets
> >   toolsoftrade: Employ new scheme for snippets of lock.c
> >   toolsoftrade: Employ new scheme for snippet of rwlockscale.c
> >   toolsoftrade: Employ new scheme for snippet of compiler barriers
> >   toolsoftrade: Employ new scheme for snippets of threadcreate.c
> >   count: Fix indent in count_lim_atomic.c
> > 
> >  CodeSamples/api-pthreads/api-pthreads.h |   7 +-
> >  CodeSamples/count/count_lim_atomic.c    |   2 +-
> >  CodeSamples/intro/threadcreate.c        |  20 +-
> >  CodeSamples/toolsoftrade/lock.c         |  76 +++---
> >  CodeSamples/toolsoftrade/rwlockscale.c  |  54 ++--
> >  count/count.tex                         |  89 +++---
> >  toolsoftrade/toolsoftrade.tex           | 460 ++++++++------------------------
> >  7 files changed, 253 insertions(+), 455 deletions(-)
> > 
> 


      reply	other threads:[~2018-10-27  5:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 15:22 [PATCH 0/7] count, toolsoftrade: Employ new code-snippet scheme (cont.) Akira Yokosawa
2018-10-26 15:24 ` [PATCH 1/7] count: Employ new scheme for inline code snippets Akira Yokosawa
2018-10-26 15:24 ` [PATCH 2/7] toolsoftrade: Use 'VerbatimU' for inline snippets Akira Yokosawa
2018-10-26 15:26 ` [PATCH 3/7] toolsoftrade: Employ new scheme for snippets of lock.c Akira Yokosawa
2018-10-26 15:27 ` [PATCH 4/7] toolsoftrade: Employ new scheme for snippet of rwlockscale.c Akira Yokosawa
2018-10-26 15:28 ` [PATCH 5/7] toolsoftrade: Employ new scheme for snippet of compiler barriers Akira Yokosawa
2018-10-26 15:29 ` [PATCH 6/7] toolsoftrade: Employ new scheme for snippets of threadcreate.c Akira Yokosawa
2018-10-26 15:30 ` [PATCH 7/7] count: Fix indent in count_lim_atomic.c Akira Yokosawa
2018-10-26 15:35 ` [PATCH 0/7] count, toolsoftrade: Employ new code-snippet scheme (cont.) Akira Yokosawa
2018-10-26 20:58   ` 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=20181026205845.GZ4170@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