All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	linux-kernel@vger.kernel.org, akiyks@gmail.com,
	boqun.feng@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
	luc.maranget@inria.fr, npiggin@gmail.com, peterz@infradead.org,
	stern@rowland.harvard.edu, will.deacon@arm.com,
	davem@davemloft.net
Subject: Re: [PATCH 0/2] tools/memory-model: remove ACCESS_ONCE()
Date: Tue, 3 Jul 2018 08:53:03 -0700	[thread overview]
Message-ID: <20180703155303.GA3593@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180703101241.GA29602@andrea>

On Tue, Jul 03, 2018 at 12:12:41PM +0200, Andrea Parri wrote:
> > >   1) Merge the file touched by that patch into (the recently created):
> > >   
> > >         Documentation/atomic_t.txt
> > > 
> > >      (FWIW, queued in my TODO list).
> > 
> > Some consolidation of documentation would be good.  ;-)
> > 
> > Thoughts from others?
> > 
> > >   2) Add the entry:
> > > 
> > > 	F: Documentation/atomic_t.txt
> > > 
> > >      to the "ATOMIC INFRASTRUCTURE" subsystem in the MAINTAINERS file so
> > >      that developers can easily find (the intended?) reviewers for their
> > >      patch. (Of course, this will need ACK from the ATOMIC people).
> > 
> > If the merging will take awhile, it might also be good to put
> > Documentation/core-api/atomic_ops.rst somewhere as well.
> 
> Indeed.  And let's not forget the "orphaned":
> 
>   Documentation/atomic_bitops.txt
>   Documentation/core-api/refcount-vs-atomic.rst

Lots of puppies to adopt, aren't there?  ;-)

I could make the argument that these files are part of the documentation
for the Linux kernel's memory model, and that they should therefore be
added to the LKMM MAINTAINERS entry.  Any objections?  (Adding David
Miller in his capacity of author of atomic_ops.txt.)

Separately, it might be good to make sure that the linux-arch folks are
aware of proposed changes to the memory model.  To that end, would it
make sense to add the linux-arch mailing list to that same entry?

							Thanx, Paul

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

commit 33a58ee5eadadfb1f4850eabd4fac332984881d5
Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Date:   Tue Jul 3 08:48:09 2018 -0700

    tools/memory-model: Add informal LKMM documentation to MAINTAINERS
    
    The Linux-kernel memory model has been informal, with a number of
    text files documenting it.  It would be good to make sure that these
    informal descriptions are kept up to date and/or pruned appropriately.
    This commit therefore brings more of those text files into the LKMM
    MAINTAINERS file entry.
    
    Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
    Cc: Alan Stern <stern@rowland.harvard.edu>
    Cc: Andrea Parri <andrea.parri@amarulasolutions.com>
    Cc: Will Deacon <will.deacon@arm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Boqun Feng <boqun.feng@gmail.com>
    Cc: Nicholas Piggin <npiggin@gmail.com>
    Cc: David Howells <dhowells@redhat.com>
    Cc: Jade Alglave <j.alglave@ucl.ac.uk>
    Cc: Luc Maranget <luc.maranget@inria.fr>
    Cc: Akira Yokosawa <akiyks@gmail.com>
    Cc: Daniel Lustig <dlustig@nvidia.com>
    Cc: "David S. Miller" <davem@davemloft.net>

diff --git a/MAINTAINERS b/MAINTAINERS
index f2903b818671..2ba947fc9a2f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8321,6 +8321,10 @@ L:	linux-kernel@vger.kernel.org
 S:	Supported
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
 F:	tools/memory-model/
+F:	Documentation/atomic_bitops.txt
+F:	Documentation/atomic_t.txt
+F:	Documentation/core-api/atomic_ops.rst
+F:	Documentation/core-api/refcount-vs-atomic.rst
 F:	Documentation/memory-barriers.txt
 
 LINUX SECURITY MODULE (LSM) FRAMEWORK


  reply	other threads:[~2018-07-03 15:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 12:33 [PATCH 0/2] tools/memory-model: remove ACCESS_ONCE() Mark Rutland
2018-06-28 12:33 ` [PATCH 1/2] tools/memory-model: remove ACCESS_ONCE() from recipes Mark Rutland
2018-06-28 12:33 ` [PATCH 2/2] tools/memory-model: remove ACCESS_ONCE() from model Mark Rutland
2018-06-28 12:38 ` [PATCH 0/2] tools/memory-model: remove ACCESS_ONCE() Andrea Parri
2018-06-28 15:21   ` Paul E. McKenney
2018-06-28 16:51     ` Andrea Parri
2018-07-02 18:54       ` Paul E. McKenney
2018-07-03 10:12         ` Andrea Parri
2018-07-03 15:53           ` Paul E. McKenney [this message]
2018-07-03 17:23             ` Andrea Parri
2018-07-06 14:55               ` Paul E. McKenney
2018-06-28 22:22     ` Akira Yokosawa
2018-06-29  3:05       ` Paul E. McKenney
2018-07-07  0:17         ` LKMM patch scorecard for v4.19 merge window Paul E. McKenney
2018-07-09 18:18           ` Alan Stern
2018-07-09 23:01             ` Paul E. McKenney
2018-07-10 20:05             ` 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=20180703155303.GA3593@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akiyks@gmail.com \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=boqun.feng@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=mark.rutland@arm.com \
    --cc=npiggin@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.