No, there was a different problem that required hand patching.
> > Nope, it was added post-pre8 to final. The deactivate_page function was
> > removed completely.
>
> Look, Linus. Things should _not_ happen this way.
> Why do we add non-trivial changes when going from last -preX of a test kernel
> series to -final?
> Please make the last stable -preX the -final _without_ any changes. This is
> the third time this caused problem in recent times (2.4.11-dontuse, parport
> compile problems and now loop.o), and why don't we learn from previous
> mistakes?
> Isn't it stupid that some tarballs in the /pub/linux/kernel/v2.4/ do not even
> compile, while those in /pub/linux/kernel/testing/ does?
linux-2.4.14-pre8 did not compile either if rd.o or loop.o
were compiled as modules, but the names were changed to protect the
guilty (different symbol name, one that wasn't exported).
Maybe there should have been another -pre. But the only reason
I was staying on top of the -pre kernels was because I had several major
changes in there, this time around.
> Regards,
> Anuradha
> --
> Debian GNU/Linux (kernel 2.4.14-pre7)
-pre7 actually did compile. -pre8 did not (not without adding
a line to ksyms.c).
> I cannot conceive that anybody will require multiplications at the rate
> of 40,000 or even 4,000 per hour ...
> -- F. H. Wales (1936)
Mike
-- Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/