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.dea...@arm.com> Signed-off-by: Andrea Parri <parri.and...@gmail.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-ker...@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 <chr...@sous-sol.org> -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
