Dear Jason Cooper, On Thu, 6 Jun 2013 13:17:47 -0400, Jason Cooper wrote: > Please be aware that for-next is *not* stable. I rebuild it every time > I pull new stuff in. It's much more helpful to list only the branches > you need to build/test. Yes, I'm aware that for-next is not stable. Since the previous iteration of this patch series generated a lot of discussion, I was assuming there would be additional discussions on this new iteration, and that it would certainly not be the final version. So for ease of work, I've just based it on the branch that 'contains everything'. For sure, if I get the proper ACKs and acceptance of the general idea, I'll go ahead and send a proper version based on the correct branches. You suggested mvebu/pcie as a base, but it means I also need to merge mvebu/of_pci before that, and maybe also mvebu/pcie_bridge to have the latest changes in the PCIe driver, etc. Which is why I just went the easy/lazy way and did everything based on for-next :) Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
