From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/3] locking: Update code snippets
Date: Mon, 19 Nov 2018 09:12:31 -0800 [thread overview]
Message-ID: <20181119171231.GI4170@linux.ibm.com> (raw)
In-Reply-To: <54d29326-1695-4b98-48a7-ff9c1439f448@gmail.com>
On Tue, Nov 20, 2018 at 12:15:49AM +0900, Akira Yokosawa wrote:
> >From 0d7e7b86bf743ee1646b705f246bc50e38d23803 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Tue, 20 Nov 2018 00:03:43 +0900
> Subject: [PATCH 0/3] locking: Update code snippets
>
> Hi Paul,
>
> This is another set of patches to apply new code-snippet scheme in
> Chapter 7.
>
> Patch #1 does the simple substitutions.
>
> Patch #2 replaces remaining ACCESS_ONCE()s in Chapter 7 and
> CodeSamples/locking. It also adds a couple of READ_ONCE() and
> WRITE_ONCE() in xchglock.c.
>
> Patch #3 fixes the use of "figure" referencing code snippets.
Queued and pushed, thank you!!!
Thanx, Paul
> Thanks, Akira
> --
> Akira Yokosawa (3):
> locking: Employ new snippet scheme
> locking: Get rid of ACCESS_ONCE()
> locking: Fix reference to code snippet by "figure"
>
> CodeSamples/locking/locked_list.c | 29 ++-
> CodeSamples/locking/xchglock.c | 32 +--
> locking/locking-existence.tex | 108 ++++-----
> locking/locking.tex | 473 +++++++++++++++++---------------------
> 4 files changed, 299 insertions(+), 343 deletions(-)
>
> --
> 2.7.4
>
prev parent reply other threads:[~2018-11-20 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 15:15 [PATCH 0/3] locking: Update code snippets Akira Yokosawa
2018-11-19 15:17 ` [PATCH 1/3] locking: Employ new snippet scheme Akira Yokosawa
2018-11-19 15:19 ` [PATCH 2/3] locking: Get rid of ACCESS_ONCE() Akira Yokosawa
2018-11-19 15:21 ` [PATCH 3/3] locking: Fix reference to code snippet by "figure" Akira Yokosawa
2018-11-19 17:12 ` 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=20181119171231.GI4170@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