hverkuil: with regards to this: http://patchwork.linuxtv.org/patch/66837/
since this bug it here since 4.8, why should it be speeded up and merged on 5.9?
let's just apply it on 5.10
(or is it some serious security threat or something like that?)
It can cause a deadlock.
I have a preference for 5.9, that way I can provide backports for older long term kernels quicker.
I can live with 5.10 though, but it's not my preference.
Note that there is another patch upcoming for 5.9, reverting support for V4L2_FLAG_MEMORY_NON_CONSISTENT.
Have to leave, will be out the remainder of the afternoon.
hi all
anything for today's meeting?
hverkuil: I'll place it at the fix repo, but I don't intend to push this one alone. If other patches come for 5.9, I may send it together, hoping that Linus won't complain