locking/qrwlock: Use 'struct qrwlock' instead of 'struct __qrwlock'
authorWill Deacon <[email protected]>
Thu, 12 Oct 2017 12:20:47 +0000 (13:20 +0100)
committerIngo Molnar <[email protected]>
Wed, 25 Oct 2017 08:57:24 +0000 (10:57 +0200)
commite0d02285f16e8d5810f3d5d5e8a5886ca0015d3b
treed3d71ebf2f1727c21fcadf5b5a4c60939b3de41a
parent5a8897cc7631fa544d079c443800f4420d1b173f
locking/qrwlock: Use 'struct qrwlock' instead of 'struct __qrwlock'

There's no good reason to keep the internal structure of struct qrwlock
hidden from qrwlock.h, particularly as it's actually needed for unlock
and ends up being abstracted independently behind the __qrwlock_write_byte()
function.

Stop pretending we can hide this stuff, and move the __qrwlock definition
into qrwlock, removing the __qrwlock_write_byte() nastiness and using the
same struct definition everywhere instead.

Signed-off-by: Will Deacon <[email protected]>
Acked-by: Peter Zijlstra <[email protected]>
Cc: Boqun Feng <[email protected]>
Cc: [email protected]
Cc: Linus Torvalds <[email protected]>
Cc: Paul E. McKenney <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: Waiman Long <[email protected]>
Cc: [email protected]
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
include/asm-generic/qrwlock.h
include/asm-generic/qrwlock_types.h
kernel/locking/qrwlock.c