Adrian Bunk <bunk@xxxxxxxxxx> wrote: > That discussion is mixing two different things I suggested besides other > things before the Kconfig file was added [1]: > - have DMA_ENGINE select'ed when a device gets enabled by the user, > and not be an independent option > - switch to menuconfig and don't offer an empty kconfig menu > > There seems to be no disagreement about the former (which could > otherwise easily lead to users mistakenly enabling NET_DMA). > > The latter is more a cosmetical kconfig UI thing, and I already said > back then that it "could be dropped if it would become a problem" [2]. Ok, thanks for explaining. The menu does appear empty if I remove the architecture dependency without adding the driver...if that's a problem maybe we should do the HAVE_DMA_DEVICE thing... > So if you want to remove the architecture dependency from the DMADEVICES > menu that's OK with me. Ok, I'm gonna wait for Dan and others to respond. If it's fine with them, I'll post a patch removing the arch dependency. Haavard -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
