The patch titled sisusbvga: fix oops on disconnect has been added to the -mm tree. Its filename is sisusbvga-fix-oops-on-disconnect.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: sisusbvga: fix oops on disconnect From: Will Newton <will.newton@xxxxxxxxx> Remove the message printed with dev_info on disconnect after sisusb_dev has potentially been zeroed by sisusb_delete. The message does not provide any extra information over that which the USB subsystem prints as standard so just kill it. Signed-off-by: Will Newton <will.newton@xxxxxxxxx> Cc: Greg Kroah-Hartman <gregkh@xxxxxxx> Cc: Felipe Balbi <felipe.lima@xxxxxxxxxxx> Cc: Thomas Winischhofer <thomas@xxxxxxxxxxxxxxxx> Cc: <stable@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/usb/misc/sisusbvga/sisusb.c | 2 -- 1 file changed, 2 deletions(-) diff -puN drivers/usb/misc/sisusbvga/sisusb.c~sisusbvga-fix-oops-on-disconnect drivers/usb/misc/sisusbvga/sisusb.c --- a/drivers/usb/misc/sisusbvga/sisusb.c~sisusbvga-fix-oops-on-disconnect +++ a/drivers/usb/misc/sisusbvga/sisusb.c @@ -3264,8 +3264,6 @@ static void sisusb_disconnect(struct usb /* decrement our usage count */ kref_put(&sisusb->kref, sisusb_delete); - - dev_info(&sisusb->sisusb_dev->dev, "Disconnected\n"); } static struct usb_device_id sisusb_table [] = { _ Patches currently in -mm which might be from will.newton@xxxxxxxxx are sisusbvga-fix-oops-on-disconnect.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html