Message ID | 4EAB1BFF.3070406@gmail.com |
---|---|
State | New |
Headers | show |
On Friday 28 October 2011, Rob Herring wrote: > Here's an updated pull request to fix missing export.h include. Now it's > also dependent on module.h clean-up branch: > > git://openlinux.windriver.com/people/paulg/linux-next for-sfr > > > The following changes since commit fa1d6d372245a160eecf5f57d64d2b21ea248e08: > > Merge branch 'for-sfr' of > git://openlinux.windriver.com/people/paulg/linux-next into HEAD > (2011-10-28 15:51:07 -0500) > > are available in the git repository at: > > git://sources.calxeda.com/kernel/linux.git gic-dt I've pulled it and am now trying to clean up the mess resulting from having the previous version in a number of branches already. Can you check that the highbank/soc branch is ok this time? Arnd
On Friday 28 October 2011, Rob Herring wrote: > Merge branch 'for-sfr' of > git://openlinux.windriver.com/people/paulg/linux-next into HEAD > (2011-10-28 15:51:07 -0500) > Rob, I think there is no chance that this is working out. I've just spent a few hours trying to resolve all the dependencies from this, but I don't think it will work out, unless Linus pulls that tree very soon, which I think is very unlikely. Have you made sure that Paul even considers this branch stable? Normally this kind of change gets pushed *last* in the merge window, to make it possible to fix up all the stuff that breaks. This means I cannot wait for the branch to get merged upstream before send a pull request for my next/dt and next/soc branches. Do you even depend on that branch? It seems to me that you merely have a conflict, not a dependency, so why do you even try fixing it up? Arnd