Upstream first policy
Posted Jun 3, 2010 5:47 UTC (Thu) by alonz
In reply to: Upstream first policy
Parent article: A suspend blockers post-mortem
Yet another point—many kernel developers will not accept "upstream" code without a clear, demonstrable use-case (usually on actual hardware).
So embedded developers are stuck in a chicken-and-egg situation: they cannot ship working systems without a working kernel, and the (upstream) kernel will not accept required changes without seeing these systems.
to post comments)