The only difference between test_and_set_bit() & test_and_set_bit_lock() is memory ordering barrier semantics - the former provides a full barrier whilst the latter only provides acquire semantics. We can therefore implement test_and_set_bit() in terms of test_and_set_bit_lock() with the addition of the extra memory barrier. Do this in order to avoid duplicating logic. Signed-off-by: Paul Burton <paul.burton@mips.com> Cc: linux-mips@vger.kernel.org Cc: Huacai Chen <chenhc@lemote.com> Cc: Jiaxun Yang <jiaxun.yang@flygoat.com> Cc: linux-kernel@vger.kernel.org |
||
---|---|---|
.. | ||
bitops.c | ||
bswapdi.c | ||
bswapsi.c | ||
csum_partial.S | ||
delay.c | ||
dump_tlb.c | ||
iomap_copy.c | ||
iomap-pci.c | ||
libgcc.h | ||
Makefile | ||
memcpy.S | ||
memset.S | ||
mips-atomic.c | ||
multi3.c | ||
r3k_dump_tlb.c | ||
strncpy_user.S | ||
strnlen_user.S | ||
uncached.c |