Jerry Van Baren wrote:
Wolfgang Denk wrote:
In message 8B11A571-3BC2-42BD-9B66-DF22A736A3A7@kernel.crashing.org you wrote:
And the whole point of my patch was to enable the ability to dynamically grow the blob before we do anything w/the ramdisk.
So what is the state of this patch now? Will it go in through the FDT custodian repo, or has it been rejected, or am I supposed to apply it directly? Or?
[...]
Most of the email exchanges were with me and the patch is fine IMHO.
I was expecting it to go through the "new-image" custodian, but I would be happy to apply it to the u-boot-fdt repo and push it up from there.
Jerry, Kumar,
I think it would be better to have this patch (and other ones by Kumar that touch booting-related code) go through the new-image branch. Otherwise we'll have merge conflicts down the road, especially since we've got a big patch coming, that adds framework for new image handling. I'd like to have this framework patch merged first, then take care of (re-based) boot-related patches that have been posted recently.
Regards, Bartlomiej