Hi David, * David Herrmann <dh.herrmann@xxxxxxxxx> [2013-02-24 19:36:52 +0100]: > 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@xxxxxxxxx> > --- > include/net/bluetooth/bluetooth.h | 2 +- > net/bluetooth/af_bluetooth.c | 15 +++------------ > 2 files changed, 4 insertions(+), 13 deletions(-) Patch has been applied to bluetooth-next. Thanks. Gustavo -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
