[PATCH] 2.3.41 - config options not starting with CONFIG_

From: James Manning (jmm@raleigh.ibm.com)
Date: Sat Jan 29 2000 - 16:25:49 EST


[ Saturday, January 29, 2000 ] James Manning wrote:
> [ Saturday, January 29, 2000 ] Michael Elizabeth Chastain wrote:
> > You are correct: config options have to start with CONFIG_ in order for
> > config dependencies to work. The bad part is that they will fail silently
> > with no errors (if someone reconfigures and changes one of these symbols,
> > the affected files will not be rebuilt).
>
> Ouch. Time to patch them back to CONFIG_* names :)

Here is the patch (attached). Of the 5 broken options, 3
were only in Configure.help (CONFIG_IDEDMA_NEW_DRIVE_LISTINGS,
CONFIG_PDC202XX_FORCE_MASTER_MODE, CONFIG_PDC202XX_FORCE_BURST_BIT)
and 2 were broken in all places (CONFIG_HPT366_FAST_IRQ_PREDICTION,
CONFIG_HPT366_MODE3).

James

-- 
Miscellaneous Engineer --- IBM Netfinity Performance Development


- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 21:00:24 EST