Messages in this thread | | | Date | Wed, 16 May 2007 08:44:59 -0700 | From | "Paul E. McKenney" <> | Subject | Re: How to force Kconfig tristate into range n..m? |
| |
On Wed, May 16, 2007 at 02:18:48PM +0200, Andi Kleen wrote: > > > > > Is there some other way to prohibit modules from being compiled into > > the main kernel? > > One way is to use a separate symbol that is not user visible, but depends > on your main symbol and uses default m > > (similar to the now infamous CONFIG_SCSI_WAIT_SCAN)
Cool!!! Any problem you see with Randy Dunlap's suggestion of simply adding "depends on m", though?
Thanx, Paul - 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/
| |