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/4] Update snippets of litmus tests
Date: Thu, 29 Nov 2018 16:22:40 -0800	[thread overview]
Message-ID: <20181130002240.GP4170@linux.ibm.com> (raw)
In-Reply-To: <fc9a8cff-4982-e97e-7437-5edcc401ce7f@gmail.com>

On Fri, Nov 30, 2018 at 07:10:15AM +0900, Akira Yokosawa wrote:
> >From f07d05ca837a57e07f7a87bcbac2bf034905adab Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Fri, 30 Nov 2018 06:55:25 +0900
> Subject: [PATCH 0/4] Update snippets of litmus tests
> 
> Hi Paul,
> 
> RCU litmus tests recently added in "formal" did not compile
> by klitmus7. Patch #1 is my attempt to manage them klitmus7
> ready.
> 
> Patch #2 add recipe for klitmus7-ready tests. Such tests need
> to be manually added in a list.
> 
> In preparing Patch #3, I looked up your "litmus" repository
> and found that comments on "exists" clause are actually allowed
> in the form of "(* ... *)".  Patch #3 updates labels embedded
> in litmus tests. Patch #4 updates styleguide accordingly.
> 
>         Thanks, Akira

Queued and pushed, thank you!

And yes, I sometimes use existing litmus tests as reference manuals.

							Thanx, Paul

> --
> Akira Yokosawa (4):
>   formal: Make RCU litmus tests klitmus7 ready
>   CodeSamples/formal/herd: Add recipe for klitmus7-ready tests
>   Use '(* ... *)' style comments in epilogue of litmus tests
>   styleguide: Loosen restriction on comment in litmus test
> 
>  CodeSamples/formal/herd/C-RCU-remove.litmus        | 18 +++++---
>  .../formal/herd/C-RomanPenyaev-list-rcu-rr.litmus  | 28 ++++++++----
>  .../formal/herd/C-SB+l-o-o-u+l-o-o-u-C.litmus      |  4 +-
>  CodeSamples/formal/herd/Makefile                   |  6 ++-
>  appendix/styleguide/styleguide.tex                 | 25 ++++-------
>  utilities/reorder_ltms.pl                          | 50 ++++++----------------
>  6 files changed, 57 insertions(+), 74 deletions(-)
> 
> -- 
> 2.7.4
> 


      parent reply	other threads:[~2018-11-30 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 22:10 [PATCH 0/4] Update snippets of litmus tests Akira Yokosawa
2018-11-29 22:11 ` [PATCH 1/4] formal: Make RCU litmus tests klitmus7 ready Akira Yokosawa
2018-11-29 22:12 ` [PATCH 2/4] CodeSamples/formal/herd: Add recipe for klitmus7-ready tests Akira Yokosawa
2018-11-29 22:14 ` [PATCH 3/4] Use '(* ... *)' style comments in epilogue of litmus tests Akira Yokosawa
2018-11-29 22:15 ` [PATCH 4/4] styleguide: Loosen restriction on comment in litmus test Akira Yokosawa
2018-11-30  0:22 ` 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=20181130002240.GP4170@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