summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorJonathan McDowell <noodles@earth.li>2008-11-04 07:51:38 +0000
committerJeff Garzik <jgarzik@redhat.com>2008-11-07 03:33:45 -0500
commit939a9516416ad8ccec27aa05bd19236c550c0c03 (patch)
tree552191a16f56e63407934b064f96c983f5fa14f1 /scripts
parentcd17fa7b8f1dd24b23c464ebcb14e7c058e15097 (diff)
downloadlinux-939a9516416ad8ccec27aa05bd19236c550c0c03.tar.gz
linux-939a9516416ad8ccec27aa05bd19236c550c0c03.tar.bz2
linux-939a9516416ad8ccec27aa05bd19236c550c0c03.zip
[netdrvr] usb/hso: Cleanup rfkill error handling
Yup, this appears to be the problem, thanks. I think &hso_net->net->dev is more intuitive for the error message, so I've used that. I've also added missing line endings on the error messages and set our local rfkill structure element to NULL on failure so we don't try to call rfkill_unregister on driver removal if we failed to register at all. The patch below Works For Me (TM); the device is detected fine, can be removed without problems and connects ok. I'll have a prod at why the rfkill stuff isn't working next, but I believe this cleanup of the error handling is appropriate no matter what the issue with registration is. Signed-Off-By: Jonathan McDowell <noodles@earth.li> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions