On Tue, Jun 28, 2016 at 11:09:42AM +0800, Alex Hung wrote: What triggered this patch? Was an error/panic observed? Is this a theoretical bug or an observed one? This will impact if it goes back to stable. Please provide a complete change log. > Signed-off-by: Alex Hung <alex.hung@xxxxxxxxxxxxx> > --- > drivers/platform/x86/intel-hid.c | 5 ++--- > 1 file changed, 2 insertions(+), 3 deletions(-) > > diff --git a/drivers/platform/x86/intel-hid.c b/drivers/platform/x86/intel-hid.c > index a818db6..ed58742 100644 > --- a/drivers/platform/x86/intel-hid.c > +++ b/drivers/platform/x86/intel-hid.c > @@ -122,8 +122,8 @@ static int intel_hid_input_setup(struct platform_device *device) > return 0; > > err_free_device: > - input_free_device(priv->input_dev); > - return ret; > + input_free_device(priv->input_dev); > + return ret; > } > > static void intel_hid_input_destroy(struct platform_device *device) > @@ -224,7 +224,6 @@ static int intel_hid_remove(struct platform_device *device) > acpi_remove_notify_handler(handle, ACPI_DEVICE_NOTIFY, notify_handler); > intel_hid_input_destroy(device); > intel_hid_set_enable(&device->dev, 0); > - acpi_remove_notify_handler(handle, ACPI_DEVICE_NOTIFY, notify_handler); > > /* > * Even if we failed to shut off the event stream, we can still > -- > 2.7.4 > > -- Darren Hart Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
