be next to KVM and Xen.
I agree, I can try to work on that too, as it would nicely complement
the menuconfigifcation.
--
Vincent Legoll
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
, not change
the config dependencies.
v2: added "default y" to avoid breaking existing configs
Signed-off-by: Vincent Legoll <vincent.leg...@gmail.com>
---
drivers/hv/Kconfig | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/hv/Kconfig b/drivers/
Hello,
The following patch add a "default y" to the menuconfig to avoid breaking
existing configs.
Please advise if this is better, and sufficient.
Tell me if these kind of changes are not welcome in the kernel, so that I
won't continue with other similar work. I am an actual user of
s (if any) for that series too (this one is not alone,
I've got a bunch of other similar patches in-flight)
Thanks
--
Vincent Legoll
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
, not change
the config dependencies.
Signed-off-by: Vincent Legoll <vincent.leg...@gmail.com>
---
drivers/hv/Kconfig | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/hv/Kconfig b/drivers/hv/Kconfig
index 50b89ea0e60f..5804081d936d 100644
--- a/drivers/hv/Kconfig
No need to get into the submenu to disable all ANDROID-related config entries
Signed-off-by: Vincent Legoll <vincent.leg...@gmail.com>
---
drivers/android/Kconfig | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/android/Kconfig b/drivers/android/Kconfig
years ago, I now have to take tens of minutes
going through all. This work is a step trying to make this step quicker.
Is that better ?
Thanks
--
Vincent Legoll
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
o 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
