Bluetooth: Use proper datatypes in release-callbacks
This enhances code readability a lot and avoids using void* even though we know the type of the variable. Signed-off-by: David Herrmann <dh.herrmann@googlemail.com> Acked-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
3dc07322b1
commit
2dd106887d
@ -79,8 +79,8 @@ static const struct attribute_group *bt_link_groups[] = {
|
||||
|
||||
static void bt_link_release(struct device *dev)
|
||||
{
|
||||
void *data = to_hci_conn(dev);
|
||||
kfree(data);
|
||||
struct hci_conn *conn = to_hci_conn(dev);
|
||||
kfree(conn);
|
||||
}
|
||||
|
||||
static struct device_type bt_link = {
|
||||
@ -368,8 +368,8 @@ static const struct attribute_group *bt_host_groups[] = {
|
||||
|
||||
static void bt_host_release(struct device *dev)
|
||||
{
|
||||
void *data = to_hci_dev(dev);
|
||||
kfree(data);
|
||||
struct hci_dev *hdev = to_hci_dev(dev);
|
||||
kfree(hdev);
|
||||
module_put(THIS_MODULE);
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user