On Tue, Apr 12, 2022 at 03:55:21AM -0300, Bruno Moreira-Guedes wrote:
> Currently, the VME_USER driver is in the staging tree Kconfig, unlike
> other VME drivers already moved to the main portions of the kernel tree.
> Its configuration is, however, nested into the VME_BUS config option,
> which might be misleading.
>
> Since the staging tree "[...] is used to hold stand-alone[1] drivers and
> filesystem that are not ready to be merged into the main portion of the
> Linux kernel tree [...]"[1], IMHO all staging drivers should appear
> nested into the Main Menu -> Device Drivers -> Staging Drivers to make
> sure the user don't pick it without being fully aware of its staging
> status as it could be the case in Menu -> Device Drivers -> VME bridge
> support (the current location).
>
> With this change menuconfig users will clearly know this is not a driver
> in the main portion of the kernel tree and decide whether to build it or
> not with that clearly in mind.
>
> This change goes into the same direction of commit 4b4cdf3979c3
> ("STAGING: Move staging drivers back to staging-specific menu")
>
> CHANGELOG
> v1:
> - Sourced "drivers/staging/vme/devices/Kconfig" in
> "drivers/staging/Kconfig" and unsourced in "drivers/vme/Kconfig".
>
> v2:
> - Turned into a patchset to (1) fix missing "depends on" missing entry
> in config VME_USER at "drivers/staging/vme/devices/Kconfig",
> affecting the behavior of this patch, and (2) fix unnecessary
> remaining files from the time the whole vme subtree was in staging.
Changelog goes below the --- line please.
> REFERENCES
> [1] https://lkml.org/lkml/2009/3/18/314
Never reference lkml.org, we have no control over it and it goes down a
lot. Please use lore.kernel.org links, and put the link in the body of
the text, no need for footnotes.
thanks,
greg k-h
