> I was in your position, I feel it may be a mistake. > I personaly do not trust the 2.4.x kernel entirely yet, and would > prefer to > wait for 2.4.1 or 2.4.2 before upgrading from 2.2.18 to ensure last-minute > wrinkles have been completely ironed out, and I know there are people who > share my viewpoint, and would rather use 2.2.XX for a while yet, and I'm > afraid that this may partialy criple 2.2 driver development. I would wait for at least 2.4.10 on production systems (servers in particular). Not to start a flame or anything (yeah, right), but 2.2.x was not usable on such systems before it reached 2.2.16 IMHO. So, I guess, the "crippling" of driver submissions could hurt me bit, in theory, which I don't like. ;-) -- André. Alfred? http://www.tomt.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Change of policy for future 2.2 driver submissions Alan Cox
- Re: Change of policy for future 2.2 driver submis... Nicholas Knight
- Re: Change of policy for future 2.2 driver su... Mark Hahn
- Re: Change of policy for future 2.2 drive... Daniel Phillips
- Re: Change of policy for future 2.2 driver su... Tim Riker
- RE: Change of policy for future 2.2 driver su... Andre Tomt
- RE: Change of policy for future 2.2 drive... Gerhard Mack
- Re: Change of policy for future 2.2 driver su... Rik van Riel
- Fw: Change of policy for future 2.2 driver submis... Nicholas Knight
- Re: Fw: Change of policy for future 2.2 drive... Mike Galbraith
- Re: Fw: Change of policy for future 2.2 drive... Mark Hahn
- Re: Change of policy for future 2.2 driver submis... Michael D. Crawford
- Re: Change of policy for future 2.2 driver su... Miles Lane
- Re: Change of policy for future 2.2 driver su... Linus Torvalds
- Re: Change of policy for future 2.2 drive... Hubert Mantel