On Sat, 16 Sep 2017, Rob Landley wrote: > So, I added a workaround with a printk in hopes of embarassing them into > someday fixing it. Oh, it will be fixed in Debian alright. I am just waiting the issue to settle a bit to file the bug reports, or maybe even send in the Debian patches myself (note that I am not responsible for the code in question, so I am not wearing a brown paperbag at this time). Even if I didn't do it, there are several other Debian Developers reading LKML that could do it (provided they noticed this specific thread and are aware of the situation) :p I can even push for the fixes to be accepted into the stable and oldstable branches of Debian, but that can take anything from a few weeks to several months, due to the way our stable releases work. But it would eventually happen. Whether such fixes will ever make it to LTS branches, especially Ubuntu's, *that* I don't know. -- Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
