Bob Copeland 26925042b6 ath5k: manipulate rxlink and descriptor address under rxbuf lock ... Grabbing an ath5k_buf then dropping the lock is racy because the referenced descriptor can be obtained in another thread and released before the buffer is handed to the hardware. Likewise, manipulating sc->rxlink without the lock can lead to having multiple self-linked hardware descriptors. Changes-licensed-under: 3-Clause-BSD Signed-off-by: Bob Copeland <me@bobcopeland.com> Acked-by: Nick Kossifidis <mickflemm@gmail.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>		2009-04-22 16:57:15 -04:00
..
ath5k.h
attach.c
base.c	ath5k: manipulate rxlink and descriptor address under rxbuf lock	2009-04-22 16:57:15 -04:00
base.h	ath5k: use rx hw descriptor pointer for self-linked check	2009-04-22 16:57:14 -04:00
caps.c
debug.c
debug.h
desc.c
desc.h
dma.c	ath5k: use rx hw descriptor pointer for self-linked check	2009-04-22 16:57:14 -04:00
eeprom.c
eeprom.h
gpio.c
initvals.c	ath5k: fix initvals errors	2009-04-22 16:57:14 -04:00
Kconfig
led.c	ath5k: add support for Fukato Datacask Jupiter LEDs	2009-04-22 16:54:41 -04:00
Makefile
pcu.c
phy.c	ath5k: fix interpolation with equal power levels	2009-04-22 16:54:40 -04:00
qcu.c
reg.h
reset.c
rfbuffer.h
rfgain.h