Commit-ID: ea52d698c1ed0c4555656de0dd1f7ac5866f89e1 Gitweb: https://git.kernel.org/tip/ea52d698c1ed0c4555656de0dd1f7ac5866f89e1 Author: Andrea Parri <parri.andrea@xxxxxxxxx> AuthorDate: Tue, 20 Feb 2018 15:25:03 -0800 Committer: Ingo Molnar <mingo@xxxxxxxxxx> CommitDate: Wed, 21 Feb 2018 09:58:13 +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 <will.deacon@xxxxxxx> Signed-off-by: Andrea Parri <parri.andrea@xxxxxxxxx> Signed-off-by: Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx> Acked-by: Peter Zijlstra <peterz@xxxxxxxxxxxxx> Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx> Cc: akiyks@xxxxxxxxx Cc: boqun.feng@xxxxxxxxx Cc: dhowells@xxxxxxxxxx Cc: j.alglave@xxxxxxxxx Cc: linux-arch@xxxxxxxxxxxxxxx Cc: luc.maranget@xxxxxxxx Cc: nborisov@xxxxxxxx Cc: npiggin@xxxxxxxxx Cc: stern@xxxxxxxxxxxxxxxxxxx Link: http://lkml.kernel.org/r/1519169112-20593-3-git-send-email-paulmck@xxxxxxxxxxxxxxxxxx Signed-off-by: Ingo Molnar <mingo@xxxxxxxxxx> --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 654c6c6..42da350 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -8163,6 +8163,7 @@ L: linux-kernel@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|