Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To:     Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc:     Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
        Mauro Carvalho Chehab <mchehab@infradead.org>,
        linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 15/39] docs: early-userspace: move to driver-api guide
Date:   Fri, 28 Jun 2019 09:30:08 -0300
Message-Id: <e5889b2b00604491c6dc32c2f2a1d5afb9200ed8.1561724493.git.mchehab+samsung@kernel.org>
In-Reply-To: <cover.1561724493.git.mchehab+samsung@kernel.org>
References: <cover.1561724493.git.mchehab+samsung@kernel.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Those documents describe a kAPI. So, add to the driver-api
book.

Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
---
 .../{ => driver-api}/early-userspace/buffer-format.rst        | 0
 .../early-userspace/early_userspace_support.rst               | 0
 Documentation/{ => driver-api}/early-userspace/index.rst      | 2 --
 Documentation/driver-api/index.rst                            | 1 +
 Documentation/filesystems/nfs/nfsroot.txt                     | 2 +-
 Documentation/filesystems/ramfs-rootfs-initramfs.txt          | 4 ++--
 usr/Kconfig                                                   | 2 +-
 7 files changed, 5 insertions(+), 6 deletions(-)
 rename Documentation/{ => driver-api}/early-userspace/buffer-format.rst (100%)
 rename Documentation/{ => driver-api}/early-userspace/early_userspace_support.rst (100%)
 rename Documentation/{ => driver-api}/early-userspace/index.rst (95%)

diff --git a/Documentation/early-userspace/buffer-format.rst b/Documentation/driver-api/early-userspace/buffer-format.rst
similarity index 100%
rename from Documentation/early-userspace/buffer-format.rst
rename to Documentation/driver-api/early-userspace/buffer-format.rst
diff --git a/Documentation/early-userspace/early_userspace_support.rst b/Documentation/driver-api/early-userspace/early_userspace_support.rst
similarity index 100%
rename from Documentation/early-userspace/early_userspace_support.rst
rename to Documentation/driver-api/early-userspace/early_userspace_support.rst
diff --git a/Documentation/early-userspace/index.rst b/Documentation/driver-api/early-userspace/index.rst
similarity index 95%
rename from Documentation/early-userspace/index.rst
rename to Documentation/driver-api/early-userspace/index.rst
index 2b8eb6132058..6f20c3c560d8 100644
--- a/Documentation/early-userspace/index.rst
+++ b/Documentation/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
index 97bab578ea72..d41d1c561f01 100644
--- 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
index 4862d3d77e27..ae4332464560 100644
--- 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
index fa985909dbca..97d42ccaa92d 100644
--- 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
index 86e37e297278..a6b68503d177 100644
--- 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.
 
-- 
2.21.0