Am 13.07.2015 um 18:47 schrieb Johan Hovold: > On Mon, Jul 13, 2015 at 06:08:50PM +0200, Michał Pecio wrote: >>> Commit 57ce61aad748 might be helpful... ;) >>> >>> Good luck, >>> Frank >>> >>> >> Pretty much the same thing I have done, except that I didn't notice that >> 0 = 512 :) >> >> Apparently, 57ce61aad748 fell victim of a mass-revert caused by some >> underdebugged issues. Is it known what they were? Is there any chance >> of getting this driver fixed again? > Yes, that series caused some regressions late in the release cycle and > was reverted so that it could get some more review and testing.
It was the baud rate divisor fix patch (only) which unveiled a single long standing bug in another part of the driver I offered you a simple and 100% safe solution for this (not reporting the actually set baud rate as before). Instead (after suddenly taking over maintainership) you decided to needlessly revert the whole series to "rediscuss things", "retest" and "clean up" things. These patches already had successfully completed the review and testing process, were applied by Greg (the maintainer at that time) and pulled by Linus. And during all these months of hard work, there had been _zero_ comments from you. > If you want to pick this up and improve the divisor calculations that'd > be great. Maybe you should just start doing your job as the maintainer and accept one of the patches people are sending to you to get this issue fixed ? Since at least 2012 lots of time and work has been invested into this by different people. But till today, there are still zero reviews and also no alternative patch from you. Your chance. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
