Re: [PATCH 11/13] selftests/powerpc: kill off ACCESS_ONCE()

2017-10-10 Thread Mark Rutland
On Tue, Oct 10, 2017 at 11:45:04AM +1100, Michael Ellerman wrote: > Mark Rutland writes: > > > For several reasons, it is desirable to use {READ,WRITE}_ONCE() in > > preference to ACCESS_ONCE(), and new code is expected to use one of the > > former. So far, there's been no

Re: [PATCH 11/13] selftests/powerpc: kill off ACCESS_ONCE()

2017-10-10 Thread Mark Rutland
On Tue, Oct 10, 2017 at 11:45:04AM +1100, Michael Ellerman wrote: > Mark Rutland writes: > > > For several reasons, it is desirable to use {READ,WRITE}_ONCE() in > > preference to ACCESS_ONCE(), and new code is expected to use one of the > > former. So far, there's been no reason to change most

Re: [PATCH 11/13] selftests/powerpc: kill off ACCESS_ONCE()

2017-10-09 Thread Michael Ellerman
Mark Rutland writes: > For several reasons, it is desirable to use {READ,WRITE}_ONCE() in > preference to ACCESS_ONCE(), and new code is expected to use one of the > former. So far, there's been no reason to change most existing uses of > ACCESS_ONCE(), as these aren't

Re: [PATCH 11/13] selftests/powerpc: kill off ACCESS_ONCE()

2017-10-09 Thread Michael Ellerman
Mark Rutland writes: > For several reasons, it is desirable to use {READ,WRITE}_ONCE() in > preference to ACCESS_ONCE(), and new code is expected to use one of the > former. So far, there's been no reason to change most existing uses of > ACCESS_ONCE(), as these aren't currently harmful. > >

[PATCH 11/13] selftests/powerpc: kill off ACCESS_ONCE()

2017-10-09 Thread Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in preference to ACCESS_ONCE(), and new code is expected to use one of the former. So far, there's been no reason to change most existing uses of ACCESS_ONCE(), as these aren't currently harmful. However, for some features it is

[PATCH 11/13] selftests/powerpc: kill off ACCESS_ONCE()

2017-10-09 Thread Mark Rutland
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in preference to ACCESS_ONCE(), and new code is expected to use one of the former. So far, there's been no reason to change most existing uses of ACCESS_ONCE(), as these aren't currently harmful. However, for some features it is