Andre Hedrick wrote:
> Well blame that on the folks that are not taking kernel code that will
> allow you to solve this problem. Linus is the number one offender.
Linus is taking some patches and not others right now... so what? A
couple of my patches, isolated and clearly unrelated to bio and mochel's
driver work, made it in. Others got dropped.
I see several people (not just you Andre) whining about the dropped
patches, when it seems to clear to me that only a few things in specific
areas are getting applied right now. For you specifically, Andre, Jen's
patches have been slated for 2.5.x for a while, so it seems blindingly
obvious that he would not take your IDE patches at least until the bio
subsystem is finished and clean, since you IDE patches would clearly
depend on the bio changes.
I do not believe this as a personal condemnation of your patches, or
bcrl's, or anyone else's.
Patience is a virtue ;-) We have a long devel series in front of us
and we are only at the pre-patches to the FIRST 2.5.x release.
-- Jeff Garzik | Only so many songs can be sung Building 1024 | with two lips, two lungs, and one tongue. MandrakeSoft | - nomeansno - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:30 EST