Re: [PATCH] spin_lock_*(): Always evaluate second argument

2014-07-21 Thread David Rientjes
On Mon, 16 Jun 2014, Bart Van Assche wrote: > Evaluating a macro argument only if certain configuration options > have been selected is confusing and error-prone. Hence always > evaluate the second argument of spin_lock_nested() and > spin_lock_nest_lock(). > > This patch has the intentional side

Re: [PATCH] spin_lock_*(): Always evaluate second argument

2014-06-16 Thread David Rientjes
On Mon, 16 Jun 2014, Bart Van Assche wrote: > Evaluating a macro argument only if certain configuration options > have been selected is confusing and error-prone. Hence always > evaluate the second argument of spin_lock_nested() and > spin_lock_nest_lock(). > > This patch has the intentional side

[PATCH] spin_lock_*(): Always evaluate second argument

2014-06-16 Thread Bart Van Assche
Evaluating a macro argument only if certain configuration options have been selected is confusing and error-prone. Hence always evaluate the second argument of spin_lock_nested() and spin_lock_nest_lock(). This patch has the intentional side effect that it avoids that the following warning is repo