On Wed, Feb 20, 2013 at 12:25 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > Hi Julian, > >> > What might be interesting is for drivers to somehow indicate they >> > support it? But you wouldn't necessarily want drivers to "select MESH", >> > so it'd probably have to be something like not allowing mesh to be >> > turned on if no driver is turned on that has it? But that makes it >> > complicated again, so it's all probably not worth it. >> >> IIRC, the standard way to do things like that is something like: >> >> config HAVE_MESH_DRIVER >> default n >> >> config RANDOM_DRIVER >> select HAVE_MESH_DRIVER >> >> config MESH >> default y if HAVE_MESH_DRIVER >> >> That way it's default on if drivers are selected which have mesh >> support but still user selectable (either to disable or if out-of-tree >> drivers want it). > > Ah, yes, I was thinking something like that but forgot about the > "default ... if" syntax and gave up trying to reproduce it with "select" > and "depends on" :-) > > That seems like the best of both worlds? Thomas? Yes it's nice we can leave out mesh when not useful, will put this in the PATCH. Do you think it will be alright if I go ahead and add the 'select' to all supported drivers in the same patch? -- Thomas -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
