On 4/3/06, Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > Greg Freemyer wrote: > > On 4/3/06, Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > > > >> For the record, I do consider irq-pio upstream ready. It still needs to > >> wait for Tejun's EH work to make it upstream, to give upstream people > >> the test sets of > >> > >> - prep EH (2.6.17-rc1) > >> - EH > >> - NCQ > >> - irq-pio > >> > >> Since each of these sets is staged, upstream testers will be able to say > >> "2.6.17-rc1 works, but 2.6.18-git1 doesn't", which gives us a lot of > >> good info. > >> > >> Jeff > > > > So for those of us anxiously waiting for the above great enhancements > > it looks like it will be 5 months or so before it is in a released > > vanilla kernel? ie. assuming 2 1/2 months per kernel release. > > Heavens no :) > > The stages above just need to be separated out by a few 2.6.X-gitX or > 2.6.X-rcX releases. > > Jeff I'm confused. You just poseted: > Due to the merge window closing, the three pending patchsets will be in > 2.6.18. That sure sounds like 5 months before it is in a released vanilla kernel. ie. it has been taking about 10 weeks per kernel release. 2.6.17 is likely to take another 8 weeks. Then 10 weeks for 2.6.18 to come out. It seems that the only way around it is to petition Linus to get as much of the above into 2.6.17 as possible. Somehow I doubt that will be successful, but I don't monitor LKML, so I don't know if he ever responds to requests like that or not. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century - : send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
