FYI... Starting with v2.6.29, I am going to be focusing primarily on getting the DaVinci core code into changesets that can be submitted upstream. With the goal of getting large parts of the DaVinci core merged in the 2.6.30 merge window.
To that end, I have created a 'davinci-upstream' git tree[1] which will track Linus' upstream tree and where I will be staging upstream-bound branches. The master branch of this tree will directly track Linus' tree. DaVinci code will be in various staging branches and these branches will be rebased and reworked as necessary. Note: THESE BRANCHES WILL *NOT* BE STABLE DEVELOPMENT BRANCHES The current DaVinci git tree will remain the place where stable development will continue based on the 2.6.28 kernel. I will continue to review and merge patches against that tree, albiet with lower priority than the upstream push. Currently, there are two branches: 1) upstream/drivers: this will track driver-related patches that are bound for upstream. 2) upstream/staging: This currently holds one big, ugly patch which contains all DaVinci core changes (arch/arm/*) from the DaVinci git tree up until the v2.6.28-davinci1 tag. I will now begin breaking apart the big-ugly-patch into pieces that are ready for submission upstream. Kevin [1] git://git.kernel.org/pub/scm/linux/kernel/git/khilman/davinci-upstream.git _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
