From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751770AbeBDKL5 (ORCPT ); Sun, 4 Feb 2018 05:11:57 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:56204 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750827AbeBDKLr (ORCPT ); Sun, 4 Feb 2018 05:11:47 -0500 Date: Sun, 4 Feb 2018 02:11:49 -0800 From: "Paul E. McKenney" To: Andrea Parri Cc: corbet@lwn.net, stern@rowland.harvard.edu, 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, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH 2/2] MAINTAINERS: list file memory-barriers.txt within the LKMM entry Reply-To: paulmck@linux.vnet.ibm.com References: <1517562822-6293-1-git-send-email-parri.andrea@gmail.com> <20180202235102.GC3617@linux.vnet.ibm.com> <20180203010800.GA6570@andrea> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180203010800.GA6570@andrea> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 x-cbid: 18020410-0044-0000-0000-000003DB3AEA X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00008468; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000248; SDB=6.00984745; UDB=6.00499598; IPR=6.00764116; BA=6.00005811; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00019359; XFM=3.00000015; UTC=2018-02-04 10:11:45 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18020410-0045-0000-0000-0000080AA8B1 Message-Id: <20180204101149.GP3617@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-02-03_07:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1802040134 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 03, 2018 at 02:08:00AM +0100, Andrea Parri wrote: > On Fri, Feb 02, 2018 at 03:51:02PM -0800, Paul E. McKenney wrote: > > On Fri, Feb 02, 2018 at 10:13:42AM +0100, Andrea Parri wrote: > > > Now that a formal specification of the LKMM has become available to > > > the developer, some concern about how to track changes to the model > > > on the level of the "high-level documentation" was raised. > > > > > > A first "mitigation" to this issue, suggested by Will, is to assign > > > maintainership (and responsibility!!) of such documentation (here, > > > memory-barriers.txt) to the maintainers of the LKMM themselves. > > > > > > Suggested-by: Will Deacon > > > Signed-off-by: Andrea Parri > > > > Very good, thank you, queued! Please see below for the usual commit-log > > rework. BTW, in future submissions, could you please capitalize the > > first word after the colon (":") in the subject line? It is all too > > easy for me to forget to change this, as Ingo can attest. ;-) > > Sorry, I'll do my best! ;-) > > > > > > If we are going to continue to use the LKMM acronym, should we make the > > first line of the MAINTAINERS block look something like this? > > I've no strong opinion about whether we should, but it makes sense to me. > (The acronym is currently defined (and heavily used) in explanation.txt.) I have added an experimental commit to this effect (see the "EXP" at the beginning of the subject line). If there are no objections, I will squash it into 12a62a1d0703 ("MAINTAINERS: Add the Memory Consistency Model subsystem"). Thanx, Paul > Thanks, > Andrea > > > > > > LINUX KERNEL MEMORY CONSISTENCY MODEL (LKMM) > > > > One alternative would be to start calling it LKMCM, though that does > > look a bit like a Roman numeral. ;-) > > > > Thanx, Paul > > > > ------------------------------------------------------------------------ > > > > commit 2f80571625dc2d1977acdef79267ba1645b07c53 > > Author: Andrea Parri > > Date: Fri Feb 2 10:13:42 2018 +0100 > > > > MAINTAINERS: List file memory-barriers.txt within the LKMM entry > > > > We now have a shiny new Linux-kernel memory model (LKMM) and the old > > tried-and-true Documentation/memory-barrier.txt. It would be good to > > keep these automatically synchronized, but in the meantime we need at > > least let people know that they are related. Will suggested adding the > > Documentation/memory-barrier.txt file to the LKMM maintainership list, > > thus making the LKMM maintainers responsible for both the old and the new. > > This commit follows Will's excellent suggestion. > > > > Suggested-by: Will Deacon > > Signed-off-by: Andrea Parri > > Signed-off-by: Paul E. McKenney > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index ba4dc08fbe95..e6ad9b44e8fb 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -8101,6 +8101,7 @@ 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/memory-barriers.txt > > > > LINUX SECURITY MODULE (LSM) FRAMEWORK > > M: Chris Wright > > >