Hello, >> No need to get into the submenu to disable all ANDROID-related config entries > > I don't understand this, what exactly do you mean? This is intended for people using make menuconfig to tailor their kernel config to their need by disabling all options they don't need. In order to have a smaller kernel, for example, but also to get smaller build times. So what this patch (and the others I also sent) is doing: There was a "menu", under which you have some config entries. In order to disable any or all of those config entries, you have to enter the submenu to then select each one and disable it. With a menuentry (and config options depending on it), you get a way to disable all those config entries at once without having to enter the menu. Does that make sense ? Is there a better way to achieve the disabling-easiness goal ? Any input appreciated. Thanks -- Vincent Legoll _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
