>>>>> "Muli" == Muli Ben-Yehuda <[EMAIL PROTECTED]> writes:

    Muli> On Mon, Dec 30, 2002 at 01:50:21PM +0200, Aharon Schkolnik
    Muli> 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 ?

    Muli> If you're talking about cpufreq, it has been merged in 2.5,
    Muli> but not (AFAIK) in 2.4.


Hmm. If it hasn't been merged, wonder how I ended up with it ?

    Muli> I see that you were compiling 2.4.18-19.8.0. That's not a
    Muli> numbering scheme I'm familiar with - where did you get this
    Muli> kernel? is this a distribution kernel?


RedHat update.


    >> Isn't that a normal course of events for kernel changes ?

    Muli> Not necessarily. Some get merged, some don't, depending on
    Muli> their technical quality, ability to solve a real world
    Muli> probelm, code quality and maintainer's outlook. Then, we
    Muli> have numerous kernel trees, each with a different maintainer
    Muli> and a different policy of what gets in and what doesn't.


Of course, but what I meant is that it is normal for a patch to be
merged into the kernel source, and then cease to be a patch.

    >> If it has been incorporated into the kernel, shouldn't it be
    >> documented ?

    Muli> In an ideal world, yes. In the Linux kernel development
    Muli> world... unfortunately not always.

Of course.


    >> If it doesn't work as a module, shouldn't it be impossible to
    >> build it as a module ?

    Muli> In a stable kernel release, definitely. In a development
    Muli> kernel, again, not necessarily.

Wonder if RedHat is "releasing" (as an update) development kernels.


    >> Seems to me that someone slipped up here.

    Muli> Send a bug report... it never hurts. But send it to the
    Muli> maintainer of 2.4.18-19.8.0, whoever that is.


Well, I'm willing to do my part.

Could someone point me in the right direction for sending in a bug
report on this. Who does it need to go to ? Is there a fixed format ?




-- 
  The day is short, and the work is great,  |  Aharon Schkolnik
  and the laborers are lazy, and the reward |  Israel Health Ministry 
  is great, and the Master of the house is  |  [EMAIL PROTECTED]
  impatient. - Ethics Of The Fathers Ch. 2  |  +972 2 670 6954/5

=================================================================
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]

Reply via email to