Re: PATCH 2.4.14 mregparm=3 compilation fixes

Christoph Hellwig
2001-11-12T16:27:00Z

In article <4300.1005581402@ocs3.intra.ocs.com.au> you wrote:
> Setting mregparm must be a CONFIG_ option, with a huge warning that
>
> A) Changing CONFIG_MREGPARM requires make mrproper.

The above patch changes the kernel to always use mregparm -
it should be catched by the .flags depencies anyway.

> B) Loading binary only modules into a kernel compiled with mregparm is
> even more likely to destroy your kernel.

Nope - people who uses those are just doomed.

Christoph

--
Of course it doesn't work. We've performed a software upgrade.