Re: [RFC] spinlock_t & rwlock_t break_lock member initialization (patch seeking comments included)

2005-04-04 Thread Zwane Mwaikambo
On Mon, 28 Mar 2005, Jesper Juhl wrote: > On Sun, 27 Mar 2005, Zwane Mwaikambo wrote: > > > On Sun, 27 Mar 2005, Jesper Juhl wrote: > > > > > I've now been running kernels (both PREEMPT, SMP, both and without both) > > > with the patch below applied for a few days and I see no ill effects. I'm

Re: [RFC] spinlock_t rwlock_t break_lock member initialization (patch seeking comments included)

2005-04-04 Thread Zwane Mwaikambo
On Mon, 28 Mar 2005, Jesper Juhl wrote: On Sun, 27 Mar 2005, Zwane Mwaikambo wrote: On Sun, 27 Mar 2005, Jesper Juhl wrote: I've now been running kernels (both PREEMPT, SMP, both and without both) with the patch below applied for a few days and I see no ill effects. I'm still

Re: [RFC] spinlock_t & rwlock_t break_lock member initialization (patch seeking comments included)

2005-03-27 Thread Jesper Juhl
On Sun, 27 Mar 2005, Zwane Mwaikambo wrote: > On Sun, 27 Mar 2005, Jesper Juhl wrote: > > > I've now been running kernels (both PREEMPT, SMP, both and without both) > > with the patch below applied for a few days and I see no ill effects. I'm > > still interrested in comments about wether or

Re: [RFC] spinlock_t & rwlock_t break_lock member initialization (patch seeking comments included)

2005-03-27 Thread Zwane Mwaikambo
On Sun, 27 Mar 2005, Jesper Juhl wrote: > I've now been running kernels (both PREEMPT, SMP, both and without both) > with the patch below applied for a few days and I see no ill effects. I'm > still interrested in comments about wether or not something like this > makes sense and is acceptable

Re: [RFC] spinlock_t & rwlock_t break_lock member initialization (patch seeking comments included)

2005-03-27 Thread Jesper Juhl
I've now been running kernels (both PREEMPT, SMP, both and without both) with the patch below applied for a few days and I see no ill effects. I'm still interrested in comments about wether or not something like this makes sense and is acceptable ? -- Jesper Juhl On Sun, 20 Mar 2005,

Re: [RFC] spinlock_t rwlock_t break_lock member initialization (patch seeking comments included)

2005-03-27 Thread Jesper Juhl
I've now been running kernels (both PREEMPT, SMP, both and without both) with the patch below applied for a few days and I see no ill effects. I'm still interrested in comments about wether or not something like this makes sense and is acceptable ? -- Jesper Juhl On Sun, 20 Mar 2005,

Re: [RFC] spinlock_t rwlock_t break_lock member initialization (patch seeking comments included)

2005-03-27 Thread Zwane Mwaikambo
On Sun, 27 Mar 2005, Jesper Juhl wrote: I've now been running kernels (both PREEMPT, SMP, both and without both) with the patch below applied for a few days and I see no ill effects. I'm still interrested in comments about wether or not something like this makes sense and is acceptable ?

Re: [RFC] spinlock_t rwlock_t break_lock member initialization (patch seeking comments included)

2005-03-27 Thread Jesper Juhl
On Sun, 27 Mar 2005, Zwane Mwaikambo wrote: On Sun, 27 Mar 2005, Jesper Juhl wrote: I've now been running kernels (both PREEMPT, SMP, both and without both) with the patch below applied for a few days and I see no ill effects. I'm still interrested in comments about wether or not

[RFC] spinlock_t & rwlock_t break_lock member initialization (patch seeking comments included)

2005-03-20 Thread Jesper Juhl
I'm often building the tree with gcc -W to look for potential trouble spots, and of course I see a lot of warning messages. I'm well aware that most of these don't indicate actual problems and should just be ignored, but the less warnings there are the easier it is to zoom in on the ones that

[RFC] spinlock_t rwlock_t break_lock member initialization (patch seeking comments included)

2005-03-20 Thread Jesper Juhl
I'm often building the tree with gcc -W to look for potential trouble spots, and of course I see a lot of warning messages. I'm well aware that most of these don't indicate actual problems and should just be ignored, but the less warnings there are the easier it is to zoom in on the ones that