docs: early-userspace: move to driver-api guide

Those documents describe a kAPI. So, add to the driver-api book. Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
mariux64 · Jul 15, 2019 · ec4b78a · ec4b78a
1 parent 6cf2a73
commit ec4b78a
Show file tree

Hide file tree

Showing 7 changed files with 5 additions and 6 deletions.
diff --git a/...ntation/early-userspace/buffer-format.rst → ...ver-api/early-userspace/buffer-format.rst b/...ntation/early-userspace/buffer-format.rst → ...ver-api/early-userspace/buffer-format.rst
diff --git a/...rly-userspace/early_userspace_support.rst → ...rly-userspace/early_userspace_support.rst b/...rly-userspace/early_userspace_support.rst → ...rly-userspace/early_userspace_support.rst
diff --git a/Documentation/early-userspace/index.rst → ...tion/driver-api/early-userspace/index.rst b/Documentation/early-userspace/index.rst → ...tion/driver-api/early-userspace/index.rst
@@ -1,5 +1,3 @@
-:orphan:
-
 ===============
 Early Userspace
 ===============

diff --git a/Documentation/driver-api/index.rst b/Documentation/driver-api/index.rst
@@ -16,6 +16,7 @@ available subsections can be seen below.
 
    basics
    infrastructure
+   early-userspace/index
    pm/index
    clk
    device-io

diff --git a/Documentation/filesystems/nfs/nfsroot.txt b/Documentation/filesystems/nfs/nfsroot.txt
@@ -239,7 +239,7 @@ rdinit=<executable file>
   A description of the process of mounting the root file system can be
   found in:
 
-    Documentation/early-userspace/early_userspace_support.rst
+    Documentation/driver-api/early-userspace/early_userspace_support.rst
 
 
 

diff --git a/Documentation/filesystems/ramfs-rootfs-initramfs.txt b/Documentation/filesystems/ramfs-rootfs-initramfs.txt
@@ -105,7 +105,7 @@ All this differs from the old initrd in several ways:
   - The old initrd file was a gzipped filesystem image (in some file format,
     such as ext2, that needed a driver built into the kernel), while the new
     initramfs archive is a gzipped cpio archive (like tar only simpler,
-    see cpio(1) and Documentation/early-userspace/buffer-format.rst).  The
+    see cpio(1) and Documentation/driver-api/early-userspace/buffer-format.rst).  The
     kernel's cpio extraction code is not only extremely small, it's also
     __init text and data that can be discarded during the boot process.
 
@@ -159,7 +159,7 @@ One advantage of the configuration file is that root access is not required to
 set permissions or create device nodes in the new archive.  (Note that those
 two example "file" entries expect to find files named "init.sh" and "busybox" in
 a directory called "initramfs", under the linux-2.6.* directory.  See
-Documentation/early-userspace/early_userspace_support.rst for more details.)
+Documentation/driver-api/early-userspace/early_userspace_support.rst for more details.)
 
 The kernel does not depend on external cpio tools.  If you specify a
 directory instead of a configuration file, the kernel's build infrastructure

diff --git a/usr/Kconfig b/usr/Kconfig
@@ -18,7 +18,7 @@ config INITRAMFS_SOURCE
 	  When multiple directories and files are specified then the
 	  initramfs image will be the aggregate of all of them.
 
-	  See <file:Documentation/early-userspace/early_userspace_support.rst> for more details.
+	  See <file:Documentation/driver-api/early-userspace/early_userspace_support.rst> for more details.
 
 	  If you are not sure, leave it blank.