summaryrefslogtreecommitdiffstats
path: root/Documentation/driver-api
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2022-06-06 10:41:05 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-06-10 15:38:14 +0200
commit35ba63b8f6d07d353159505423cfca5a4378a11c (patch)
treee30e8a9dc55b5e935e212b32b4bec38787b51189 /Documentation/driver-api
parent3493536142000805c1492a0d9d5b6c03a725711d (diff)
downloadlinux-stable-35ba63b8f6d07d353159505423cfca5a4378a11c.tar.gz
linux-stable-35ba63b8f6d07d353159505423cfca5a4378a11c.tar.bz2
linux-stable-35ba63b8f6d07d353159505423cfca5a4378a11c.zip
vme: move back to staging
The VME subsystem graduated from staging into a top-level subsystem in 2012, with commit db3b9e990e75 ("Staging: VME: move VME drivers out of staging") stating: The VME device drivers have not moved out yet due to some API questions they are still working through, that should happen soon, hopefully. However, this never happened: maintenance of drivers/vme effectively stopped in 2017, with all subsequent changes being treewide cleanups. No hardware driver remains in staging, only the limited user-level access, and I just removed one of the two bridge drivers and the only remaining board. drivers/staging/vme/devices/ was recently moved to drivers/staging/vme_user/, but as the vme_user driver is the only one remaining for this subsystem, it is easier to just move the remaining three source files into this directory rather than keeping the original hierarchy. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Link: https://lore.kernel.org/r/20220606084109.4108188-3-arnd@kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/driver-api')
-rw-r--r--Documentation/driver-api/vme.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/driver-api/vme.rst b/Documentation/driver-api/vme.rst
index def139c13410..c0b475369de0 100644
--- a/Documentation/driver-api/vme.rst
+++ b/Documentation/driver-api/vme.rst
@@ -290,8 +290,8 @@ The function :c:func:`vme_bus_num` returns the bus ID of the provided bridge.
VME API
-------
-.. kernel-doc:: include/linux/vme.h
+.. kernel-doc:: drivers/staging/vme_user/vme.h
:internal:
-.. kernel-doc:: drivers/vme/vme.c
+.. kernel-doc:: drivers/staging/vme_user/vme.c
:export: