USB: cxacru: Use appropriate logging for errors
authorSimon Arlott <simon@fire.lp0.eu>
Tue, 25 Sep 2007 19:20:10 +0000 (20:20 +0100)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 12 Oct 2007 21:55:28 +0000 (14:55 -0700)
commit4ac0718e83821db53451614e098399004694aa81
treef62e3fc951ec57d4f815b324049e124d3a7222d8
parent1f4f714f88955cfb61fba0cd43fe3b07e4212257
USB: cxacru: Use appropriate logging for errors

When an error occurs, existing logging uses dbg() so the cause of a
problem is hard to determine. Error conditions shouldn't only be
properly reported with debugging enabled.

A side effect of this change is that when an uninitialised device is
started, a log message similar to the following is sent:
cxacru 5-2:1.0: receive of cm 0x90 failed (-104)
This is normal - the device did not respond so firmware will be loaded.

Signed-off-by: Simon Arlott <simon@fire.lp0.eu>
Acked-by: Duncan Sands <baldrick@free.fr>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/usb/atm/cxacru.c