Greg KH <gregkh@xxxxxxx> writes: > On Fri, Jul 18, 2008 at 09:41:29PM +0900, Tejun Heo wrote: >> Greg KH wrote: >> > Ok, I'll work to get these in where applicable. >> >> Did this get into 2.6.27? Or will this have to wait till .28? > > I haven't sent any patches to Linus yet for 2.6.27, so it hasn't gotten > there yet. > > And due to the intrusiveness, and the fact that this hasn't been tested > at all in any build tree yet, I can't in good concious submit this for > .27 either. > > Part of this is my fault, I know, due to vacation and work, but also > lots is due to the fact that the code showed up so late in the > development cycle. The code showed up at least by the beginning of may, and the code has been around for 9 months or more. I just haven't always had the energy to retransmit every time it has gotten dropped. The last spin of it was very late I agree. > I'll add it to my tree, and get it some testing in the next cycle of > linux-next until 2.6.27 is out, and then if it's still looking good, go > into .28. I think that is unnecessarily precautions but reasonable. That should at least keep other sysfs patches from coming in and causing bit rot. Eric _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
