Jan Kiszka b75b2eedcb CAPI: Drop handle_minor_recv from capinc_tty_write ... Sending a message down the CAPI stack may trigger the reception of an answer, but this will go through capi_recv_message and call handle_minor_recv from there. There is no need to walk the receive queue on capinc_tty_write. Signed-off-by: Jan Kiszka <jan.kiszka@web.de> Signed-off-by: David S. Miller <davem@davemloft.net>		2010-02-16 16:01:31 -08:00
..
capi.c	CAPI: Drop handle_minor_recv from capinc_tty_write	2010-02-16 16:01:31 -08:00
capidrv.c	CAPI: Rework controller state notifier	2010-02-16 16:01:21 -08:00
capidrv.h
capifs.c	CAPI: Reduce chattiness during module loading/removal	2010-02-16 16:01:19 -08:00
capifs.h	CAPI: Sanitize capifs API	2010-02-16 16:01:18 -08:00
capilib.c
capiutil.c	trivial: remove unnecessary semicolons	2009-09-21 15:14:58 +02:00
kcapi_proc.c	CAPI: Rework application locking	2010-02-16 16:01:22 -08:00
kcapi.c	CAPI: Rework application locking	2010-02-16 16:01:22 -08:00
kcapi.h	CAPI: Rework locking of controller data structures	2010-02-16 16:01:22 -08:00
Kconfig	Kconfig: Remove useless and sometimes wrong comments	2009-11-09 09:40:56 +01:00
Makefile