quoted

quoted

Is this a bugfix that needs to go in 2.6.22?

This potentially breaks lots of other platforms, so no
please, put it in early in the next cycle and give those
others time to recover from this change.

I would expect that the bugfix is relatively harmless,

Sure, but you cannot prove that without checking all possibly
affected systems' device trees, that's my whole point.  If
you need a fix for .22 you can always put a conditional on
celleb around the offending code.  Anyway, Paul's choice.


Segher