e136e3036b
Checking tty == NULL doesn't help us unless we have a clear semantic for the locking of the tty object in the driver. Use the tty kref objects so that we can take references to the tty in the USB event handling paths. Signed-off-by: Alan Cox <alan@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
|---|---|---|
| .. | ||
| asix.c | ||
| catc.c | ||
| cdc_ether.c | ||
| cdc_subset.c | ||
| dm9601.c | ||
| gl620a.c | ||
| hso.c | ||
| kaweth.c | ||
| Kconfig | ||
| Makefile | ||
| mcs7830.c | ||
| net1080.c | ||
| pegasus.c | ||
| pegasus.h | ||
| plusb.c | ||
| rndis_host.c | ||
| rtl8150.c | ||
| smsc95xx.c | ||
| smsc95xx.h | ||
| usbnet.c | ||
| zaurus.c | ||