> Is this fixed with the latest 2.6.31-15 that was delivered today?
No. It would be nice to know what was the reason not to apply the ready-to-use patch to 2.6.31-15, even if it was intended to rebase to 2.6.31.5 or 2.6.31.6 later.
> Is this fixed with the latest 2.6.31-15 that was delivered today?
No. It would be nice to know what was the reason not to apply the ready-to-use patch to 2.6.31-15, even if it was intended to rebase to 2.6.31.5 or 2.6.31.6 later.