Commit 1e5c5946 authored May 28, 2008 by surinder Committed by Russell King Jun 02, 2008

[ARM] 5067/1: _raw_write_can_lock macro bugfix



The current __raw_write_can_lock macro tests whether the lock can be
locked by checking if it is equal to 0x80000000, whereas the lock
should be lockable if its value is 0 i.e. unlocked state is
represented by 0. Hence the macro should test the value of lock
against 0 and not 0x80000000.

Signed-off-by: Surinder Pal Singh <srplsnh@gmail.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>

parent ea6a7404

include/asm-arm/spinlock.h

+1 −1

Original line number	Diff line number	Diff line
		@@ -142,7 +142,7 @@ static inline void __raw_write_unlock(raw_rwlock_t *rw)
		}

		/* write_can_lock - would write_trylock() succeed? */
		#define __raw_write_can_lock(x) ((x)->lock == 0x80000000)
		#define __raw_write_can_lock(x) ((x)->lock == 0)

		/*
		* Read locks are a bit more hairy: