On 05/17/2010 12:24 AM, Benjamin Herrenschmidt wrote: > On Sun, 2010-05-16 at 23:11 -0700, Yinghai wrote: >> so looks like your change will hit 2.6.35, and my x86 changes will hit >> 2.6.36? >> >> that is too long. > > No. Both will hit 2.6.36. It's way too late to queue up such changes for > the 2.6.35 merge window which has already opened. i have feeling that your new LMB code will hit 2.6.36. and x86 patches that is using to lmb will hit 2.6.37. otherwise it will make more merge conflicts between tip and lmb. unless put your lmb change to tip? > > Why would it be "too long" ? I keep asking what the heck is going on > with having a time bomb on those patches and yet have to get a > satisfactory answer. why are you thinking that there is time bomb in the patches? I even provide the option to use x86 own low to high allocation. really don't know where is the time bomb. my -v14 patches only touch several lines your core lmb code, and have near 0 affect to original lmb users. YH -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html