diff options
author | Bruno Moreira-Guedes <codeagain@codeagain.dev> | 2022-04-21 11:59:34 -0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-04-22 16:47:29 +0200 |
commit | e36c9c00188458d4843d68cae947e64d99259b0e (patch) | |
tree | ee970b794683ee57932e5561dda303171f002fe8 /drivers/staging/vme_user/Kconfig | |
parent | 3da709f3efe5557bf4af8dd4f1a02b1c854ad119 (diff) |
staging: vme: Move 'vme/devices/' to 'vme_user/'
In <db3b9e990e75573402cda22faf933760f076c033> ("Staging: VME: move VME
drivers out of staging") the vme code, board and bridge drivers were
moved out of the staging tree, remaining only the VME user device
driver.
Since this driver is the only one remaining in staging, such multi-level
structure confuses more than helps. The current structure is as follows:
- drivers/staging/vme/
Makefile
devices/
Kconfig
Makefile
vme_user.c
vme_user.h
The top-level Makefile has the only function of calling another Makefile
into the devices/ subdirectory. This latter only compiles the vme_user
driver, since there is no other in the staging tree.
This patch removes the unnecessary Makefile from the 'vme/' dir, move
the contents of 'vme/devices' into the 'vme/' dir, and renames it to
'vme_user/' (the driver name), allowing a straightforward understanding
of this driver's contents. Furthermore, it updates the MAINTAINERS file
to properly reflect the new paths.
Signed-off-by: Bruno Moreira-Guedes <codeagain@codeagain.dev>
Link: https://lore.kernel.org/r/2cd7de9a426c443a5ea618682d605ecfd751d798.1650544175.git.codeagain@codeagain.dev
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/vme_user/Kconfig')
-rw-r--r-- | drivers/staging/vme_user/Kconfig | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/drivers/staging/vme_user/Kconfig b/drivers/staging/vme_user/Kconfig new file mode 100644 index 000000000000..e8b4461bf27f --- /dev/null +++ b/drivers/staging/vme_user/Kconfig @@ -0,0 +1,13 @@ +# SPDX-License-Identifier: GPL-2.0 +comment "VME Device Drivers" + +config VME_USER + tristate "VME user space access driver" + depends on STAGING && VME_BUS + help + If you say Y here you want to be able to access a limited number of + VME windows in a manner at least semi-compatible with the interface + provided with the original driver at <http://www.vmelinux.org/>. + + To compile this driver as a module, choose M here. The module will + be called vme_user. If unsure, say N. |