On Mon, May 5, 2014 at 2:59 PM, Fabio Estevam festevam@gmail.com wrote:
On Mon, May 5, 2014 at 1:46 PM, Stephen Warren swarren@wwwdotorg.org wrote:
Albert,
I was wondering when the next pull request for u-boot-arm/master -> u-boot/master was likely to be?
I asked because some changes to the Tegra USB driver went through the u-boot-tegra/master and hence are now in u-boot-arm/master, but not in u-boot-usb/master. I have some more USB driver changes which rely on the earlier USB patches, and these should really go through u-boot-usb/master rather than the Tegra/ARM tree. For this to happen, u-boot-usb/master needs to contain the patches currently in u-boot-arm/master, and the best way for that to happen is for those patches to get into u-boot/master so that u-boot-usb/master can merge them.
Or, should Marek just merge u-boot-arm/master into his tree directly?
Or should we have a 'u-boot-next' tree using the same concept as the kernel 'linux-next'?
Please, u-boot-next!
It is clear we need this to scale the pull model.