Re: [PATCH 2/2] compiler: Prevent evaluation of WRITE_ONCE()

2019-05-24 Thread Andrea Parri
On Fri, May 24, 2019 at 11:53:40AM +0100, Mark Rutland wrote: > > This would be better titled as: > > compiler: don't return a value from WRITE_ONCE() No strong opinion here: I'll adopt your suggestion in v2 if there are no objections. And similarly for the rcu_assign_pointer() patch. > >

Re: [PATCH 2/2] compiler: Prevent evaluation of WRITE_ONCE()

2019-05-24 Thread Mark Rutland
This would be better titled as: compiler: don't return a value from WRITE_ONCE() ... since we do want the WRITE_ONCE() itself to be evaluated. On Fri, May 24, 2019 at 12:35:36PM +0200, Andrea Parri wrote: > Now that there's no single use of the value of WRITE_ONCE(), change > the

[PATCH 2/2] compiler: Prevent evaluation of WRITE_ONCE()

2019-05-24 Thread Andrea Parri
Now that there's no single use of the value of WRITE_ONCE(), change the implementation to eliminate it. Suggested-by: Mark Rutland Signed-off-by: Andrea Parri Cc: Arnd Bergmann Cc: Greg Kroah-Hartman Cc: Jorgen Hansen Cc: Peter Zijlstra Cc: Will Deacon Cc: Mark Rutland Cc: "Paul E.