diff options
| author | Jingkui Wang <jkwang@google.com> | 2016-12-13 00:51:46 +0300 |
|---|---|---|
| committer | Sasha Levin <alexander.levin@verizon.com> | 2017-01-15 17:49:52 +0300 |
| commit | ad6be98aa49eb7fc66c4718a34d3e32daa3063ab (patch) | |
| tree | 37e1f78c15273a8ebccf30277645631afd54deec /fs/block_dev.c | |
| parent | 2eb056b54b6a3dd0345c50c7f0d93dab031c13a3 (diff) | |
| download | linux-ad6be98aa49eb7fc66c4718a34d3e32daa3063ab.tar.xz | |
Input: drv260x - fix input device's parent assignment
[ Upstream commit 5a8a6b89c15766446d845671d574a9243b6d8786 ]
We were assigning I2C bus controller instead of client as parent device.
Besides being logically wrong, it messed up with devm handling of input
device. As a result we were leaving input device and event node behind
after rmmod-ing the driver, which lead to a kernel oops if one were to
access the event node later.
Let's remove the assignment and rely on devm_input_allocate_device() to
set it up properly for us.
Signed-off-by: Jingkui Wang <jkwang@google.com>
Fixes: 7132fe4f5687 ("Input: drv260x - add TI drv260x haptics driver")
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Diffstat (limited to 'fs/block_dev.c')
0 files changed, 0 insertions, 0 deletions