All of lore.kernel.org
 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/6] defer: Employ new scheme for code snippets (cont.)
Date: Mon, 3 Dec 2018 09:23:32 -0800	[thread overview]
Message-ID: <20181203172332.GL4170@linux.ibm.com> (raw)
In-Reply-To: <c5c96e55-3106-1580-2930-c2f5168a7a79@gmail.com>

On Tue, Dec 04, 2018 at 12:33:32AM +0900, Akira Yokosawa wrote:
> Hi Paul,
> 
> This is a followup patch set to update remaining code snippets
> in chapter "defer".
> 
> My first thought was that patches #5 and #6 might conflict with
> upcoming updates to reflect consolidation of RCU flavors, but it
> looks like these code snippets are unlikely to be affected.
> 
> Patch #1 assumes that you intentionally presented a different
> set of hazptr API from the one used in hazptr.h.
> 
>         Thanks, Akira

Applied and pushed, thank you!

							Thanx, Paul

> --
> Akira Yokosawa (6):
>   defer: Employ new scheme for 'lst:defer:Hazard-Pointer Storage and
>     Erasure'
>   defer: Employ new scheme for snippets of route_hazptr.c
>   defer: Employ new scheme for snippet of seqlock.h
>   defer: Employ new scheme for snippets of route_seqlock.c
>   defer: Employ new scheme for snippets in rcuintro and rcufundamental
>   defer: Employ new scheme for snippets of route_rcu.c
> 
>  CodeSamples/defer/route_hazptr.c  |  50 ++--
>  CodeSamples/defer/route_rcu.c     |  75 +++---
>  CodeSamples/defer/route_seqlock.c |  56 ++--
>  CodeSamples/defer/seqlock.h       |  55 ++--
>  defer/hazptr.tex                  | 168 +++---------
>  defer/rcufundamental.tex          | 381 +++++++++++++--------------
>  defer/rcuintro.tex                |  13 +-
>  defer/rcuusage.tex                | 523 ++++++++++++++++----------------------
>  defer/seqlock.tex                 | 259 ++++++-------------
>  9 files changed, 637 insertions(+), 943 deletions(-)
> 
> -- 
> 2.7.4
> 


      parent reply	other threads:[~2018-12-03 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 15:33 [PATCH 0/6] defer: Employ new scheme for code snippets (cont.) Akira Yokosawa
2018-12-03 15:35 ` [PATCH 1/6] defer: Employ new scheme for 'lst:defer:Hazard-Pointer Storage and Erasure' Akira Yokosawa
2018-12-03 15:37 ` [PATCH 2/6] defer: Employ new scheme for snippets of route_hazptr.c Akira Yokosawa
2018-12-03 15:39 ` [PATCH 3/6] defer: Employ new scheme for snippet of seqlock.h Akira Yokosawa
2018-12-03 15:41 ` [PATCH 4/6] defer: Employ new scheme for snippets of route_seqlock.c Akira Yokosawa
2018-12-03 15:42 ` [PATCH 5/6] defer: Employ new scheme for snippets in rcuintro and rcufundamental Akira Yokosawa
2018-12-03 15:44 ` [PATCH 6/6] defer: Employ new scheme for snippets of route_rcu.c Akira Yokosawa
2018-12-03 17:23 ` 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=20181203172332.GL4170@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 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.