6 Nov
2019
6 Nov
'19
5:54 p.m.
On Wed, Nov 06, 2019 at 10:49:20AM -0600, Pierre-Louis Bossart wrote:
On 11/6/19 10:29 AM, Mark Brown wrote:
On Wed, Nov 06, 2019 at 04:21:46PM +0000, Mark Brown wrote:
It's not immediately obvious if something similar is needed for -next, the relevant code has been redone since v5.4 was branched off. If something is needed someone will have to send something.
I checked that the patch applies even before Jaska's October rework, where the same bug was present. so in theory picking this fix for 5.2..5.4 would work as usual.
What I'm saying is that I did that and if the fix is still needed after the rework someone will need to send a version that applies after the rework.