[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Fri, 2 Feb 2018 10:13:42 +0100
From: Andrea Parri <parri.andrea@...il.com>
To: corbet@....net, stern@...land.harvard.edu, will.deacon@....com,
peterz@...radead.org, boqun.feng@...il.com, npiggin@...il.com,
dhowells@...hat.com, j.alglave@....ac.uk, luc.maranget@...ia.fr,
paulmck@...ux.vnet.ibm.com
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
Andrea Parri <parri.andrea@...il.com>
Subject: [PATCH 2/2] MAINTAINERS: list file memory-barriers.txt within the LKMM entry
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 <will.deacon@....com>
Signed-off-by: Andrea Parri <parri.andrea@...il.com>
---
On top of: https://marc.info/?l=linux-kernel&m=151748668632046&w=2
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 08454be9237d7..9466907aa4db1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8106,6 +8106,7 @@ L: linux-kernel@...r.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 <chrisw@...s-sol.org>
--
2.7.4
Powered by blists - more mailing lists