On Thu, Oct 4, 2012 at 8:50 PM, Rusty Russell <[email protected]> wrote: > Mimi Zohar <[email protected]> writes: >> Why? Not only have you had these patches sitting for a while, way >> before you had the kernel module patches, they've been acked/signed off >> by Kees, Serge, Eric, and myself. All security subtree maintainers. >> The module patches could have easily been built on top of Kees' small >> patches. I am really disappointed! > > Me too. > > Linus' merge window opened on Monday 1-10-2012. One week before that > was Monday 24-09-2012, which is the nominal close of my merge window. > > The patches were sent on 21-09 (Friday for you, the weekend my time). > > If I had nothing else to do on Monday, I would have applied it, but we > spent the week trying to get the module signing patches into shape :( > > If I take them now, they need to go through linux-next. That won't > happen until Monday. I want two days in linux-next, so that people who > test linux-next get a chance to find issues, so that's Wednesday before > I send to Linus, which is getting very late into the merge window. > > And keep adding two days for every trivial issue which is found :( > > It's in my modules-wip branch for 3.8.
Cool; better than not in at all. :) Thanks! -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
