summaryrefslogtreecommitdiff
path: root/net/bluetooth/rfcomm/core.c
diff options
context:
space:
mode:
authorDavid Herrmann <dh.herrmann@gmail.com>2013-02-24 19:36:52 +0100
committerGustavo Padovan <gustavo.padovan@collabora.co.uk>2013-03-08 10:38:44 -0300
commitbe9f97f04565a6c438b7521ad679870d25645475 (patch)
tree1c7af296484f24eb1350a8b7989a18a2d6adfdc7 /net/bluetooth/rfcomm/core.c
parent5e9d7f868f04106139a58212b860dcdc268ad3af (diff)
Bluetooth: change bt_sock_unregister() to return void
There is no reason a caller ever wants to check the return type of this call. _Iff_ a user successfully called bt_sock_register(), they're allowed to call bt_sock_unregister(). All other calls in the kernel (device_del, device_unregister, kfree(), ..) that are logically equivalent return void. Lets not make callers think they have to check the return type of this call and instead simply return void. We guarantee that after bt_sock_unregister() is called, the socket type _is_ unregistered. If that is not what the caller wants, they're using the wrong function, anyway. Signed-off-by: David Herrmann <dh.herrmann@gmail.com> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Diffstat (limited to 'net/bluetooth/rfcomm/core.c')
0 files changed, 0 insertions, 0 deletions