All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mutt@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
Cc: mingo@kernel.org, stern@rowland.harvard.edu,
	parri.andrea@gmail.com, will.deacon@arm.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
Subject: [PATCH RFC tools/lkmm 0/12] Reorganize RCU-related cat rules
Date: Fri, 23 Mar 2018 08:46:51 -0700	[thread overview]
Message-ID: <20180323154651.GA28363@linux.vnet.ibm.com> (raw)

Hello!

This patch series reorganizes RCU-related cat-file rules:

1.	Renames link and rcu-path to rcu-link and rb, respectively.
	This avoids unfortunate name collisions with "link" the rule and
	"link" the concept.  Courtesy of Alan Stern.

2.	Redefines "rb" in terms of rcu-fence, explicitly expressing
	the fence-like properties of RCU grace periods.  Courtesy of
	Alan Stern.

							Thanx, Paul

------------------------------------------------------------------------

 Documentation/explanation.txt |  261 +++++++++++++++++++++++++-----------------
 linux-kernel.cat              |   49 ++++---
 2 files changed, 184 insertions(+), 126 deletions(-)

             reply	other threads:[~2018-03-23 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 15:46 Paul E. McKenney [this message]
2018-03-23 15:50 ` [PATCH tools/lkmm 1/2] tools/memory-model: Rename link and rcu-path to rcu-link and rb Paul E. McKenney
2018-03-23 15:50   ` [PATCH tools/lkmm 2/2] tools/memory-model: Redefine rb in terms of rcu-fence 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=20180323154651.GA28363@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akiyks@gmail.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=mutt@linux.vnet.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --cc=will.deacon@arm.com \
    /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.