linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	stern@rowland.harvard.edu, andrea.parri@amarulasolutions.com,
	peterz@infradead.org, boqun.feng@gmail.com, npiggin@gmail.com,
	dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
	akiyks@gmail.com, mingo@kernel.org
Subject: Re: [PATCH RFC tools/memory-model] Add litmus-test naming scheme
Date: Tue, 29 May 2018 10:30:50 +0100	[thread overview]
Message-ID: <20180529093050.GB6533@arm.com> (raw)
In-Reply-To: <20180525191020.GA5914@linux.vnet.ibm.com>

Hi Paul,

On Fri, May 25, 2018 at 12:10:20PM -0700, Paul E. McKenney wrote:
> This commit documents the scheme used to generate the names for the
> litmus tests.
> 
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
>  README |  136 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 135 insertions(+), 1 deletion(-)

Whilst I think documentation like this is extremely important for users,
this feels like it's documenting how to drive parts of diy and I'm not
convinced that it belongs in the kernel source tree as long as the projects
remain separate.

Why not contribute this to the herdtools7 documentation, then just reference
that from here? That would also be helpful for other people interested in
memory models, but perhaps not interested in Linux (assuming such people
exist ;).

Cheers,

Will

  parent reply	other threads:[~2018-05-29  9:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 19:10 [PATCH RFC tools/memory-model] Add litmus-test naming scheme Paul E. McKenney
2018-05-25 19:10 ` Paul E. McKenney
2018-05-28 11:20 ` Andrea Parri
2018-05-28 11:20   ` Andrea Parri
2018-05-28 21:48   ` Paul E. McKenney
2018-05-28 21:48     ` Paul E. McKenney
2018-05-29  9:33     ` Andrea Parri
2018-05-29  9:33       ` Andrea Parri
2018-05-29 12:19       ` Paul E. McKenney
2018-05-29 12:19         ` Paul E. McKenney
2018-05-29 12:32         ` Andrea Parri
2018-05-29 12:32           ` Andrea Parri
2018-05-29  9:30 ` Will Deacon [this message]
2018-05-29  9:30   ` Will Deacon
2018-05-29 12:11   ` Paul E. McKenney
2018-05-29 12:11     ` Paul E. McKenney
2018-05-29 20:17     ` Will Deacon
2018-05-29 20:17       ` Will Deacon
2018-09-06  0:01       ` Paul E. McKenney
2018-09-06  0:01         ` Paul E. McKenney
2018-09-06 13:52         ` Will Deacon
2018-09-06 13:52           ` Will Deacon
2018-09-06 15:13           ` Paul E. McKenney
2018-09-06 15:13             ` Paul E. McKenney

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=20180529093050.GB6533@arm.com \
    --to=will.deacon@arm.com \
    --cc=akiyks@gmail.com \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=mingo@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    /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;
as well as URLs for NNTP newsgroup(s).