5 Aug
2013
5 Aug
'13
7:28 p.m.
On 08/05/2013 09:40 AM, Simon Glass wrote: ...
Yes I think we should fix the problem properly rather than just revert. I will take a look.
How long will fixing it properly take?
I've already received at least a couple reports from people outside NVIDIA and a couple from people inside NVIDIA who have been hit by this bug. Surely a revert-first-so-people-can-do-other-work approach is better so as to reduce the impact of this bug, unless you're planning on providing the fix in the same time-scale as a revert would take? (and the window on doing that has *long* gone). This is certainly the approach we use internally at NVIDIA for serious regressions like this. Reverting the revert once the real fix is available is trivial with git.