On Fri, Sep 28, 2012 at 02:12:54PM +0100, Lorenzo Pieralisi wrote:
Ok, understood, sorry. What's the best way forward then ?
Should I add the fix for xscale and feroceon to your patch system ?
That's one solution, and probably the best as it means less commits in
the end.
Another solution is that I assume all changes I receive are bad, and
delay publishing my tree until the overnight tests have run, which adds
something like another 24 hours (or more) to the linux-next latency for
changes committed to my tree.