MAINTAINERS: add the Memory Consistency Model subsystem
Andrea Parri
maintainerPATCH 2/2 MAINTAINERS: add the Memory Consistency Model subsystem
Integrate (and then remove) tools/memory-model/MAINTAINERS into the main MAINTAINERS file. This way get_maintainer.pl can give a "right answer" for tools/memory-model/.
--- MAINTAINERS | 16 ++++++++++++++++ tools/memory-model/MAINTAINERS | 15 --------------- 2 files changed, 16 insertions(+), 15 deletions(-) delete mode 100644 tools/memory-model/MAINTAINERS
MAINTAINERS +16 -0
@@ -8091,6 +8091,22 @@ M: Kees Cook <[email protected]> S: Maintained F: drivers/misc/lkdtm* +LINUX KERNEL MEMORY CONSISTENCY MODEL +M: Alan Stern <[email protected]> +M: Andrea Parri <[email protected]> +M: Will Deacon <[email protected]> +M: Peter Zijlstra <[email protected]> +M: Boqun Feng <[email protected]> +M: Nicholas Piggin <[email protected]> +M: David Howells <[email protected]> +M: Jade Alglave <[email protected]> +M: Luc Maranget <[email protected]> +M: "Paul E. McKenney" <[email protected]> +L: [email protected] +S: Supported +T: git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git +F: tools/memory-model/ + LINUX SECURITY MODULE (LSM) FRAMEWORK M: Chris Wright <[email protected]> L: [email protected]
tools/memory-model/MAINTAINERS deleted +0 -15
@@ -1,15 +0,0 @@ -LINUX KERNEL MEMORY CONSISTENCY MODEL -M: Alan Stern <[email protected]> -M: Andrea Parri <[email protected]> -M: Will Deacon <[email protected]> -M: Peter Zijlstra <[email protected]> -M: Boqun Feng <[email protected]> -M: Nicholas Piggin <[email protected]> -M: David Howells <[email protected]> -M: Jade Alglave <[email protected]> -M: Luc Maranget <[email protected]> -M: "Paul E. McKenney" <[email protected]> -L: [email protected] -S: Supported -T: git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git -F: tools/memory-model/
Signature · 1 line
2.7.4
Quoted 11 lines · Andrea Parri
Integrate (and then remove)
tools/memory-model/MAINTAINERSinto the mainMAINTAINERSfile. This way get_maintainer.pl can give a "right answer" fortools/memory-model/.Suggested-by Ingo Molnar <[email protected]>Signed-off-by Andrea Parri <[email protected]>--- MAINTAINERS | 16 ++++++++++++++++ tools/memory-model/MAINTAINERS | 15 --------------- 2 files changed, 16 insertions(+), 15 deletions(-) delete mode 100644 tools/memory-model/MAINTAINERS
Makes a lot more sense having this in the top-level MAINTAINERS file. It might also make sense to add:
F: Documentation/memory-barriers.txt
as a separate patch now that we have a hit-list of memory model people who can help poor old Jon (who currently gets blamed by get_maintainer.pl).
Will
Andrea Parri
maintainerQuoted 15 lines · Will Deacon
Quoted 11 lines · Andrea Parri
Integrate (and then remove)
tools/memory-model/MAINTAINERSinto the mainMAINTAINERSfile. This way get_maintainer.pl can give a "right answer" fortools/memory-model/.Suggested-by Ingo Molnar <[email protected]>Signed-off-by Andrea Parri <[email protected]>--- MAINTAINERS | 16 ++++++++++++++++ tools/memory-model/MAINTAINERS | 15 --------------- 2 files changed, 16 insertions(+), 15 deletions(-) delete mode 100644 tools/memory-model/MAINTAINERSAcked-by Will Deacon <[email protected]>
Quoted 7 lines
Makes a lot more sense having this in the top-level
MAINTAINERSfile. It might also make sense to add:F:
Documentation/memory-barriers.txtas a separate patch now that we have a hit-list of memory model people who can help poor old Jon (who currently gets blamed by get_maintainer.pl).
This does make sense to me: I'll prepare/send such a patch tomorrow.
Andrea
Quoted 2 lines
Will