On Fri, Dec 16, 2016 at 03:50:40PM +0100, Peter Zijlstra wrote:
>
>
> Chris, did this series at all depend on the other ww_mutex patches?
It is independent. My goal was to try and hit the bugs Nicolai reported.
Most of it should be covered by locktorture if we add ww_mutex support
to it.
-Chris
On Fri, Dec 16, 2016 at 03:50:40PM +0100, Peter Zijlstra wrote:
>
>
> Chris, did this series at all depend on the other ww_mutex patches?
It is independent. My goal was to try and hit the bugs Nicolai reported.
Most of it should be covered by locktorture if we add ww_mutex support
to it.
-Chris
Chris, did this series at all depend on the other ww_mutex patches?
Chris, did this series at all depend on the other ww_mutex patches?
>From conflicting macro parameters, passing the wrong name to
__MUTEX_INITIALIZER and a stray '\', #define __WW_MUTEX_INITIALIZER was
very unhappy.
One unnecessary change was to choose to pass _class instead of
implicitly taking the address of the class within the macro.
Fixes: 1b375dc30710
>From conflicting macro parameters, passing the wrong name to
__MUTEX_INITIALIZER and a stray '\', #define __WW_MUTEX_INITIALIZER was
very unhappy.
One unnecessary change was to choose to pass _class instead of
implicitly taking the address of the class within the macro.
Fixes: 1b375dc30710
6 matches
Mail list logo
