pt., 10 maj 2019 o 11:16 Bartosz Golaszewski <brgl@xxxxxxxx> napisaÅ(a):
År., 8 maj 2019 o 09:13 Richard Weinberger <richard@xxxxxx> napisaÅ(a):Hi Richard, Anton,
----- UrsprÃngliche Mail -----Hi,
It works here too. That's why I never noticed.Can you please check?I am looking at it. It passed tests in my case (I did the usual round).
This patch is already queued in -next. So we need to decide whether to
revert or fix it now.
Yesterday I noticed just because I looked for something else in the kernel logs.
Thanks,
//richard
sorry for the late reply - I just came back from vacation.
I see it here too, I'll check if I can find the culprit and fix it today.
Bart
I'm not sure yet what this is caused by. It doesn't seem to break
anything for me but since it's a new error message I guess it's best
to revert this patch (others are good) and revisit it for v5.3.
--
Bart