Commit ff0e9ee3 authored by Lee Jones's avatar Lee Jones Committed by Benjamin Tissoires

HID: hid-sensor-hub: Move 'hsdev' description to correct struct definition

Fixes the following W=1 kernel build warning(s):

 drivers/hid/hid-sensor-hub.c:54: warning: Function parameter or member 'hsdev' not described in 'hid_sensor_hub_callbacks_list'

Cc: Jiri Kosina <jikos@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org
Cc: linux-iio@vger.kernel.org
Signed-off-by: default avatarLee Jones <lee.jones@linaro.org>
Acked-by: default avatarJonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: default avatarBenjamin Tissoires <benjamin.tissoires@redhat.com>
parent 07b34ddd
...@@ -18,7 +18,6 @@ ...@@ -18,7 +18,6 @@
/** /**
* struct sensor_hub_data - Hold a instance data for a HID hub device * struct sensor_hub_data - Hold a instance data for a HID hub device
* @hsdev: Stored hid instance for current hub device.
* @mutex: Mutex to serialize synchronous request. * @mutex: Mutex to serialize synchronous request.
* @lock: Spin lock to protect pending request structure. * @lock: Spin lock to protect pending request structure.
* @dyn_callback_list: Holds callback function * @dyn_callback_list: Holds callback function
...@@ -41,6 +40,7 @@ struct sensor_hub_data { ...@@ -41,6 +40,7 @@ struct sensor_hub_data {
* struct hid_sensor_hub_callbacks_list - Stores callback list * struct hid_sensor_hub_callbacks_list - Stores callback list
* @list: list head. * @list: list head.
* @usage_id: usage id for a physical device. * @usage_id: usage id for a physical device.
* @hsdev: Stored hid instance for current hub device.
* @usage_callback: Stores registered callback functions. * @usage_callback: Stores registered callback functions.
* @priv: Private data for a physical device. * @priv: Private data for a physical device.
*/ */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment