On Mon, Dec 30, 2002 at 01:50:21PM +0200, Aharon Schkolnik wrote: > >>>>> "Oleg" == Oleg Goldshmidt <[EMAIL PROTECTED]> writes: > > Oleg> Aharon Schkolnik <[EMAIL PROTECTED]> writes: Not only > Oleg> that, I could not even find anything related in the code > Oleg> (2.4.20 though). Out of curiosity, where did you find it? > >> Google search > > Oleg> Oh, it's a patch... ;-) > > Wouldn't it be more correct to say that it WAS a patch which has since > been incorporated into the mainstream kernel code ?
If you're talking about cpufreq, it has been merged in 2.5, but not (AFAIK) in 2.4. I see that you were compiling 2.4.18-19.8.0. That's not a numbering scheme I'm familiar with - where did you get this kernel? is this a distribution kernel? > Isn't that a normal course of events for kernel changes ? Not necessarily. Some get merged, some don't, depending on their technical quality, ability to solve a real world probelm, code quality and maintainer's outlook. Then, we have numerous kernel trees, each with a different maintainer and a different policy of what gets in and what doesn't. > If it has been incorporated into the kernel, shouldn't it be > documented ? In an ideal world, yes. In the Linux kernel development world... unfortunately not always. > If it doesn't work as a module, shouldn't it be impossible to build it > as a module ? In a stable kernel release, definitely. In a development kernel, again, not necessarily. > Seems to me that someone slipped up here. Send a bug report... it never hurts. But send it to the maintainer of 2.4.18-19.8.0, whoever that is. Thanks, Muli. -- Muli Ben-Yehuda "The speed of light really is too slow nowdays." -- Alan Cox ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
