On Wed, Oct 04, 2006 at 01:45:32PM +0200, Arjan van de Ven wrote:
> > Removing it for real will be a pain for external modules.
> > They could of course detect that it is missing and then
> > drop it.
> > I would suggest to keep the #warning in 2.6.19 and only
> > remove it for real for 2.6.20.
>
> they'll have to change anyway; delaying it one release doesn't actually
> change that. And you can bet on most modules ignoring the warning anyway
> and wait until the thing really is gone... making the value that this
> extra delay has basically zero. While the cost is that more false users
> will sneak into the kernel ;(
My thoughts exactly. Since when did we give a damn about keeping
external modules compiling anyway?
> Maybe Fedora can ship with an #error here early on; an #error at least
> can provide a helpful message on how to fix it.
The #warn has been there for a few weeks in the fc6pre kernels, but it's
easily changed.
Dave
--
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
