On Fri, Nov 08, 2013 at 08:37:48AM +0100, Peter Zijlstra wrote:
> On Wed, Nov 06, 2013 at 06:29:21AM -0800, Paul E. McKenney wrote:
> > On Tue, Nov 05, 2013 at 01:10:44PM +0100, Peter Zijlstra wrote:
> > > Hi all,
> > >
> > > During Kernel Summit Dave mentioned that there wasn't a clear
On Fri, Nov 08, 2013 at 08:37:48AM +0100, Peter Zijlstra wrote:
On Wed, Nov 06, 2013 at 06:29:21AM -0800, Paul E. McKenney wrote:
On Tue, Nov 05, 2013 at 01:10:44PM +0100, Peter Zijlstra wrote:
Hi all,
During Kernel Summit Dave mentioned that there wasn't a clear maintainer
for
On Wed, Nov 06, 2013 at 06:29:21AM -0800, Paul E. McKenney wrote:
> On Tue, Nov 05, 2013 at 01:10:44PM +0100, Peter Zijlstra wrote:
> > Hi all,
> >
> > During Kernel Summit Dave mentioned that there wasn't a clear maintainer for
> > locking bits.
> >
> > To remedy this Ingo suggested gathering
On Wed, Nov 06, 2013 at 06:29:21AM -0800, Paul E. McKenney wrote:
On Tue, Nov 05, 2013 at 01:10:44PM +0100, Peter Zijlstra 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
On Tue, Nov 05, 2013 at 01:10:44PM +0100, Peter Zijlstra 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:
On Tue, Nov 05, 2013 at 01:10:44PM +0100, Peter Zijlstra 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/.
On Tue, Nov 5, 2013 at 4:10 AM, Peter Zijlstra 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
On Tue, 5 Nov 2013 14:26:09 +0100
Ingo Molnar wrote:
>
> * Steven Rostedt wrote:
>
> Also, 'kernel lock' brings me back memories of the 'big kernel lock' -
> while 'kernel locks' brings verb/noun ambiguity and visuals of
> 'kernel locks up'.
Of course "locking" is only a verb, and we get
On Tue, 05 Nov 2013 14:21:38 +0100
Maarten Lankhorst wrote:
> Congratulations! You're our early bikeshed winner for today. Please pick your
> favorite color at http://bikeshed.com
Has nothing to do with bikesheds, but more to do with bagel shops!
-- Steve
--
To unsubscribe from this list:
* Steven Rostedt wrote:
> On Tue, 05 Nov 2013 13:10:44 +0100
> Peter Zijlstra 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
> >
op 05-11-13 14:18, Steven Rostedt schreef:
> On Tue, 05 Nov 2013 13:10:44 +0100
> Peter Zijlstra 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
On Tue, 05 Nov 2013 13:10:44 +0100
Peter Zijlstra 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/.
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:
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:
On Tue, 05 Nov 2013 13:10:44 +0100
Peter Zijlstra pet...@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:
op 05-11-13 14:18, Steven Rostedt schreef:
On Tue, 05 Nov 2013 13:10:44 +0100
Peter Zijlstra pet...@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
* Steven Rostedt rost...@goodmis.org wrote:
On Tue, 05 Nov 2013 13:10:44 +0100
Peter Zijlstra pet...@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
On Tue, 05 Nov 2013 14:21:38 +0100
Maarten Lankhorst maarten.lankho...@canonical.com wrote:
Congratulations! You're our early bikeshed winner for today. Please pick your
favorite color at http://bikeshed.com
Has nothing to do with bikesheds, but more to do with bagel shops!
-- Steve
--
To
On Tue, 5 Nov 2013 14:26:09 +0100
Ingo Molnar mi...@kernel.org wrote:
* Steven Rostedt rost...@goodmis.org wrote:
Also, 'kernel lock' brings me back memories of the 'big kernel lock' -
while 'kernel locks' brings verb/noun ambiguity and visuals of
'kernel locks up'.
Of course locking
On Tue, Nov 5, 2013 at 4:10 AM, Peter Zijlstra pet...@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:
20 matches
Mail list logo
