2015-08-17 15:55 GMT-04:00 Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>: > This driver is known broken in this way, please see the many discussions > about this on the driverdevel mailing list as to what the original > developers of the code are trying to do to fix this, and attempts for > others who are also trying to clean it up in this way. Good tip! I looked up different mailing lists but didn't come across the driver development one, even though I've been sending patches to it in cc... Sorry for that. > I'm also not going to take this type of changes from anyone that does > not have the hardware to properly test it, do you have the hardware that > this driver controls? No, you're right. I'm trying to contribute with what I find I can do, but I'm still just cutting my teeth at that for the time being. I'm trying to acquire a better knowledge of kernel development to try to contribute at a deeper level in the end. I thought I could work on that, but that'll indeed be difficult to test it without the hardware. Thanks for the time you're taking to review my patches and give advices Greg! Raphaël _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
