On Mon, Jul 8, 2019 at 2:54 PM Miquel Raynal <[email protected]> wrote:
> Arnd Bergmann <[email protected]> wrote on Mon, 8 Jul 2019 14:49:39 +0200:
>
> A similar patch has been sent a few weeks ago and has been applied
> yesterday night so it should have appeared this morning in linux-next :)
>
Ok, got it. I had rebased to the latest linux-next this morning and then created
the patch when I saw the bug for the first time, but it turns out that this was
still Friday's kernel and after rebasing again, it is indeed fixed.
Arnd
