summaryrefslogtreecommitdiffstats
path: root/drivers/hid/hid-lenovo.c
diff options
context:
space:
mode:
authorBenjamin Tissoires <benjamin.tissoires@redhat.com>2019-08-12 18:27:39 +0200
committerBenjamin Tissoires <benjamin.tissoires@redhat.com>2019-08-22 17:11:58 +0200
commit87fcb6a69e54527ccaeb5878168cccdba9f6b6ae (patch)
treee0aacd9f60504384cc942f0bdbb37ae9c7f04d63 /drivers/hid/hid-lenovo.c
parent15d90b242290f228166ea79ee1cc2db6b31a2143 (diff)
downloadtalos-op-linux-87fcb6a69e54527ccaeb5878168cccdba9f6b6ae.tar.gz
talos-op-linux-87fcb6a69e54527ccaeb5878168cccdba9f6b6ae.zip
HID: do not call hid_set_drvdata(hdev, NULL) in drivers
This is a common pattern in the HID drivers to reset the drvdata. Some do it properly, some do it only in case of failure. But, this is actually already handled by driver core, so there is no need to do it manually. [for hid-sensor-hub.c] Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> [For hid-picolcd_core.c] Acked-by: Bruno Prémont <bonbons@linux-vserver.org> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Diffstat (limited to 'drivers/hid/hid-lenovo.c')
-rw-r--r--drivers/hid/hid-lenovo.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/hid/hid-lenovo.c b/drivers/hid/hid-lenovo.c
index 364bc7f11d9d..96fa2a2c2cd3 100644
--- a/drivers/hid/hid-lenovo.c
+++ b/drivers/hid/hid-lenovo.c
@@ -866,8 +866,6 @@ static void lenovo_remove_tpkbd(struct hid_device *hdev)
led_classdev_unregister(&data_pointer->led_micmute);
led_classdev_unregister(&data_pointer->led_mute);
-
- hid_set_drvdata(hdev, NULL);
}
static void lenovo_remove_cptkbd(struct hid_device *hdev)
OpenPOWER on IntegriCloud