If you are willing to be a target^H^H^Htester, then I can probably whip
up a patch to fix it.
> CONFIG_OBSOLETE is checked for by Config.in for a couple of drivers (net and
> char), but the only place it seems to be defined is for the ARM architecture.
>
> Is this deliberate? Are some of the older drivers to be phased out?
> Should there be a "bool 'Prompt for obsolete code/drivers' CONFIG_OBSOLETE"
> in the config.in for other architectures, too?
CONFIG_OBSOLETE really means "this driver is broken, don't EVER show it
in the kernel config."
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/