All of lore.kernel.org
 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] Convert code snippets to 'listing' env (SMPdesign, locking, defer)
Date: Wed, 11 Oct 2017 17:16:20 -0700	[thread overview]
Message-ID: <20171012001620.GV3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <73217c9c-6c30-1cf1-735d-0fa039dd0cc0@gmail.com>

On Thu, Oct 12, 2017 at 08:19:42AM +0900, Akira Yokosawa wrote:
> On 2017/10/11 15:56:21 -0700, Paul E. McKenney wrote:
> > On Thu, Oct 12, 2017 at 07:07:17AM +0900, Akira Yokosawa wrote:
> >> >From 096ac85c06a27b8e8895e35bb58c634869a5a979 Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiyks@gmail.com>
> >> Date: Wed, 11 Oct 2017 23:04:11 +0900
> >> Subject: [PATCH] Convert code snippets to 'listing' env (SMPdesign, locking, defer)
> >>
> >> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> > 
> > Very good, queued, thank you!
> > 
> > One question...
> > 
> > o	Figure 6.22: "SEQ Pseudocode" is still in the old style.
> > 	Ditto Figure 6.23: "SEQ Helper Pseudocode", Figure 6.26:
> > 	"Partitioned Parallel Solver Pseudocode", and Figure 6.27:
> > 	"Partitioned Parallel Helper Pseudocode".  Are these to be
> > 	handled by a later commit, or is there something problematic
> > 	about these figures?
> 
> Ah, I missed them. I'll take care of them in a later patch.

Sounds good!

							Thanx, Paul

>              Thanks, Akira
> > 
> > 							Thanx, Paul
> > 
> >> ---
> >>  SMPdesign/SMPdesign.tex       | 72 +++++++++++++++++------------------
> >>  SMPdesign/partexercises.tex   | 32 ++++++++--------
> >>  defer/defer.tex               |  8 ++--
> >>  defer/hazptr.tex              | 36 +++++++++---------
> >>  defer/rcuapi.tex              | 16 ++++----
> >>  defer/rcufundamental.tex      | 46 +++++++++++-----------
> >>  defer/rcuusage.tex            | 76 ++++++++++++++++++-------------------
> >>  defer/refcnt.tex              | 32 ++++++++--------
> >>  defer/seqlock.tex             | 52 ++++++++++++-------------
> >>  locking/locking-existence.tex | 20 +++++-----
> >>  locking/locking.tex           | 88 +++++++++++++++++++++----------------------
> >>  11 files changed, 239 insertions(+), 239 deletions(-)
> >>
> [...]
> 


      reply	other threads:[~2017-10-12  0:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 22:07 [PATCH] Convert code snippets to 'listing' env (SMPdesign, locking, defer) Akira Yokosawa
2017-10-11 22:56 ` Paul E. McKenney
2017-10-11 23:19   ` Akira Yokosawa
2017-10-12  0:16     ` 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=20171012001620.GV3521@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.