29 Nov
2018
29 Nov
'18
11:57 a.m.
On Thu, Nov 29, 2018 at 12:54:13PM +0100, Thierry Reding wrote:
This looks like the same issue that I was seeing a couple of weeks ago. There's a fix for this here:
Not sure if Ben's picked that up yet, though.
It's certainly not visible in -next and the issue is showing so guessing not.