Bug 196519
Summary: | Dell XPS 13 9360: Touchscreen does not report events | ||
---|---|---|---|
Product: | Drivers | Reporter: | Enno Boland (gottox) |
Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | regressions |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 4.13.0rc1 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Enno Boland
2017-07-28 11:08:23 UTC
On Fri, Jul 28, 2017 at 11:08:23AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=196519 > > Bug ID: 196519 > Summary: Dell XPS 13 9360: Touchscreen does not report events > Product: Drivers > Version: 2.5 > Kernel Version: 4.13.0rc1 All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release. On Fri, Jul 28, 2017 at 11:08:23AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=196519 > > Bug ID: 196519 > Summary: Dell XPS 13 9360: Touchscreen does not report events > Product: Drivers > Version: 2.5 > Kernel Version: 4.13.0rc1 All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release. FYI: This issues is tracked in the regression reports for Linux 4.13 (http://bit.ly/lnxregrep413 ) with this id: Linux-Regression-ID: lr#fe68bb Please include this line in the comment section of patches that are supposed to fix the issue. Please also mention the string once in other mailinglist threads or different bug tracking entries if you or someone else start to discuss the issue there. By including that string you make it a whole lot easier to track where an issue gets discussed and how far patches to fix it have made it. More details on this: http://bit.ly/lnxregtrackid Thx for your help. Could that be the same issue that Bug 196431 discussed? BTW: Does it still happen in latest master? There was a fix that might be relevant if this hardware ha a quirk: https://git.kernel.org/torvalds/c/cf601774c9f23078010adc9e6cd29470fafa5678 Fixed with linux4.13rc3. Thanks guys, you're awesome! |