> -----Original Message----- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Wednesday, February 08, 2012 7:12 PM > To: Jiri Kosina > Cc: KY Srinivasan; Fuzhou Chen; Haiyang Zhang; stable@vger.kernel.org > Subject: Re: FAILED: patch "[PATCH] HID: hyperv: Properly disconnect the input > device" failed to apply to 3.2-stable tree > > On Thu, Feb 09, 2012 at 12:28:48AM +0100, Jiri Kosina wrote: > > On Wed, 8 Feb 2012, gre...@linuxfoundation.org wrote: > > > > > The patch below does not apply to the 3.2-stable tree. > > > If someone wants it applied there, or to any other stable or longterm > > > tree, then please email the backport, including the original git commit > > > id to <stable@vger.kernel.org>. > > > > > > thanks, > > > > > > greg k-h > > > > > > ------------------ original commit in Linus's tree ------------------ > > > > > > >From c1c454b8691cc95aa83f19273ed7845914c70e83 Mon Sep 17 00:00:00 > 2001 > > > From: "K. Y. Srinivasan" <k...@microsoft.com> > > > Date: Wed, 18 Jan 2012 08:57:14 -0800 > > > Subject: [PATCH] HID: hyperv: Properly disconnect the input device > > > > > > When we unload the mouse driver, properly disconnect the input device. > > > > > > Signed-off-by: K. Y. Srinivasan <k...@microsoft.com> > > > Signed-off-by: Haiyang Zhang <haiya...@microsoft.com> > > > Reported-by: Fuzhou Chen <fuzho...@microsoft.com> > > > Cc: stable <stable@vger.kernel.org> > > > Signed-off-by: Jiri Kosina <jkos...@suse.cz> > > > > > > diff --git a/drivers/hid/hid-hyperv.c b/drivers/hid/hid-hyperv.c > > > index 0c33ae9..4066324 100644 > > > --- a/drivers/hid/hid-hyperv.c > > > +++ b/drivers/hid/hid-hyperv.c > > > @@ -548,6 +548,7 @@ static int mousevsc_remove(struct hv_device *dev) > > > struct mousevsc_dev *input_dev = hv_get_drvdata(dev); > > > > > > vmbus_close(dev->channel); > > > + hid_hw_stop(input_dev->hid_device); > > > hid_destroy_device(input_dev->hid_device); > > > mousevsc_free_device(input_dev); > > > > Well, as the whole driver has been moved out of staging only for 3.3-rc1, > > I think that Cc: stable is actually a mistake here, as there is no > > already-released 3.x kernel for which this would be applicable (and I > > believe we are not putting -staging patches into -stable, right?). > > No, we do take staging patches into stable, if needed. If all that I > have to do here is a simple "the file is in a different place", that's > fine. But odds are, due the number of changes in this area, it will > need more than that. > > KY, any thoughts?
I just pulled down the kernel tree for 3.2. Apart from the fact that the driver has changed location, the code in 3.2 appears to be a much older version of the the mouse driver code. I need to confirm if the bug that this patch fixed is in the mouse driver in 3.2. I will get back to you on that shortly. Regards, K. Y -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
