From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
paulmck@linux.vnet.ibm.com, oleg@redhat.com, dhowells@redhat.com,
willy@linux.intel.com, tglx@linutronix.de, airlied@gmail.com,
walken@google.com, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC 0/8] Move locking primitives into kernel/locking/
Date: Tue, 05 Nov 2013 14:21:38 +0100 [thread overview]
Message-ID: <5278F0E2.9040906@canonical.com> (raw)
In-Reply-To: <20131105081838.27c7fcd4@gandalf.local.home>
op 05-11-13 14:18, Steven Rostedt schreef:
> On Tue, 05 Nov 2013 13:10:44 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
>
>> Hi all,
>>
>> During Kernel Summit Dave mentioned that there wasn't a clear maintainer for
>> locking bits.
>>
>> To remedy this Ingo suggested gathering all the various locking primitives and
>> lockdep into a single place: kernel/locking/.
>>
>> I would further like to propose a MAINTAINERS entry like:
>>
>> LOCKING
>> M: Ingo Molnar <mingo@redhat.com>
>> M: Peter Zijlstra <peterz@infradead.org>
>> M: Oleg Nesterov <oleg@redhat.com>
>> M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
>> M: Linus Torvalds <torvalds@linux-foundation.org>
>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
>> S: Maintained
>> F: kernel/locking/
> I wonder if it should be called kernel/locks, as that's less to type,
> smaller path names, and tastes good on bagels.
>
> -- Steve
>
Congratulations! You're our early bikeshed winner for today. Please pick your favorite color at http://bikeshed.com
next prev parent reply other threads:[~2013-11-05 13:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 12:10 [RFC 0/8] Move locking primitives into kernel/locking/ Peter Zijlstra
2013-11-05 12:10 ` [RFC 1/8] locking: Move mutex " Peter Zijlstra
2013-11-05 20:26 ` Michel Lespinasse
2013-11-05 21:20 ` Peter Zijlstra
2013-11-05 21:24 ` Michel Lespinasse
2013-11-06 5:40 ` Ingo Molnar
2013-11-06 11:36 ` Ingo Molnar
2013-11-05 12:10 ` [RFC 2/8] locking: Move lockdep " Peter Zijlstra
2013-11-05 12:10 ` [RFC 3/8] locking: Move spinlock " Peter Zijlstra
2013-11-05 12:10 ` [RFC 4/8] locking: Move semaphore " Peter Zijlstra
2013-11-05 12:10 ` [RFC 5/8] locking: Move rtmutex " Peter Zijlstra
2013-11-05 12:10 ` [RFC 6/8] locking: Move rwsem " Peter Zijlstra
2013-11-05 12:10 ` [RFC 7/8] locking: Move lglocks " Peter Zijlstra
2013-11-05 12:10 ` [RFC 8/8] locking: Move percpu-rwsem " Peter Zijlstra
2013-11-05 13:18 ` [RFC 0/8] Move locking primitives " Steven Rostedt
2013-11-05 13:21 ` Maarten Lankhorst [this message]
2013-11-05 14:12 ` Steven Rostedt
2013-11-05 13:26 ` Ingo Molnar
2013-11-05 14:13 ` Steven Rostedt
2013-11-05 19:38 ` Michel Lespinasse
2013-11-06 14:29 ` Paul E. McKenney
2013-11-08 7:37 ` Peter Zijlstra
2013-11-08 23:19 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5278F0E2.9040906@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=walken@google.com \
--cc=willy@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.