On Thu, May 12, 2011 at 01:54:46PM +0200, Par-Gunnar HJALMDAHL wrote: > Hi Greg, > > I downloaded you staging tree and compared the logs for the core.h file. > Compared to linux-next tag next-20110510 it is missing 2 commits: > 4dbee6b76fffd5740e87e286f4f4c1c15901bcae > 558aa9c0d620b91a896d5e39ce8a570bed65589b > where the first one is the "oldest" one in the log and is the most > important one for my patch. What trees are these patches coming from? > Another option would be for me to fix the patch for your tree, but > then I would probably have to fix it back in a few days when you update > your staging tree to Linux-next. How often is your tree updated? linux-next pulls from my tree, I don't pull from linux-next. As I don't see those patches in Linus's tree, I can't merge my tree forward to include them yet. I could take those patches also through my tree if you want me to, or you could send this patch through the mfd tree so that things build properly there too. > The easiest is probably to wait a few days until you have the next-20110510 > tag in your tree and then apply the patch. That will never happen, see above for how linux-next works. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html