2012/3/19 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>: > On Sun, Mar 18, 2012 at 11:51:49PM +0400, tamerlan311 wrote: >> Now I encountered a small problem. New version of module backported to >> old kernel (3.2) make a panic when module try to unload. >> >> usb_serial_register_drivers >> usb_serial_deregister_drivers() >> module_usb_serial_driver() >> >> these functions just copied to private header with kernel version >> check condition. > > I doubt that will work, you needed to make some changes to the > usb-serial core as well, which is probably why you are having these > problems. > > I suggest just working on top of the linux-next tree, or my usb-next > branch, at the least, to ensure that things work properly. > > Hope this helps, > I implement usb_serial_register_drivers() and usb_serial_deregister_drivers() functions with old-style code. That work normally and don't required any changes in module, just include header with back-ported code. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
