On Wed, Feb 24, 2016 at 02:48:59PM +1100, Stephen Rothwell wrote:
On Wed, 24 Feb 2016 12:28:42 +0900 Mark Brown broonie@kernel.org wrote:
That didn't work out unfortunately, the error is still there today.
Yeah, the patch didn't hit -next yesterday and I missed the opportunity to fix in manually. However, it should be fixed in today's linux-next (out in a few hours, hopefully).
Ah, good - it was just too late rather than not working.