Filip, All, On Monday 17 January 2011 23:39:17 Filip Honckiewicz wrote: > It helped me a lot and now it's clear. Your example shows everything. > In kconfig-language.txt there is: > "This is similar to the simple config entry above, but it also gives > a hint to front ends, that all suboptions should be displayed as a > separate list of options." and this "suboptions" fool me that if > there're suboptions than there has to be ending of menuconfig entry;) Maybe expressing this in a more understandable way, such as: The menuconfig scope ends with the last config options that depends on that menuconfig entry. Is that more comprehensible? If so, maybe suggest a patch to clear up the confusion. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
