On Mon, Mar 14, 2011 at 1:37 PM, Colin Cross <ccross@xxxxxxxxxx> wrote: > I am going to push changes to tegra's for-next branch that will only > build after the asoc branch is merged, and will include a merge of a > small part of Ben's next-i2c branch. Can you move tegra after these > branches? > > Should I merge the asoc branch in below the patches that depend on it > in tegra's for-next tree, or should I push a branch that will not > build without merging into linux-next? My $.02: If you want to push a branch that's not for-next that contains the dependencies to make it easier for people to test, that might be a good option. For linux-next, if the branch is pulled by sfr after the asoc and i2c trees, the option with least hassle is to just leave it out of your branch (my board branch left them out, I just merged that branch into linux-next to test it). -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
