lkml.org 
[lkml]   [2021]   [Jul]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.13 218/223] Documentation: Fix intiramfs script name
    Date
    From: Robert Richter <rrichter@amd.com>

    commit 5e60f363b38fd40e4d8838b5d6f4d4ecee92c777 upstream.

    Documentation was not changed when renaming the script in commit
    80e715a06c2d ("initramfs: rename gen_initramfs_list.sh to
    gen_initramfs.sh"). Fixing this.

    Basically does:

    $ sed -i -e s/gen_initramfs_list.sh/gen_initramfs.sh/g $(git grep -l gen_initramfs_list.sh)

    Fixes: 80e715a06c2d ("initramfs: rename gen_initramfs_list.sh to gen_initramfs.sh")
    Signed-off-by: Robert Richter <rrichter@amd.com>
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    ---
    Documentation/driver-api/early-userspace/early_userspace_support.rst | 8 ++++----
    Documentation/filesystems/ramfs-rootfs-initramfs.rst | 2 +-
    2 files changed, 5 insertions(+), 5 deletions(-)

    --- a/Documentation/driver-api/early-userspace/early_userspace_support.rst
    +++ b/Documentation/driver-api/early-userspace/early_userspace_support.rst
    @@ -69,17 +69,17 @@ early userspace image can be built by an

    As a technical note, when directories and files are specified, the
    entire CONFIG_INITRAMFS_SOURCE is passed to
    -usr/gen_initramfs_list.sh. This means that CONFIG_INITRAMFS_SOURCE
    +usr/gen_initramfs.sh. This means that CONFIG_INITRAMFS_SOURCE
    can really be interpreted as any legal argument to
    -gen_initramfs_list.sh. If a directory is specified as an argument then
    +gen_initramfs.sh. If a directory is specified as an argument then
    the contents are scanned, uid/gid translation is performed, and
    usr/gen_init_cpio file directives are output. If a directory is
    -specified as an argument to usr/gen_initramfs_list.sh then the
    +specified as an argument to usr/gen_initramfs.sh then the
    contents of the file are simply copied to the output. All of the output
    directives from directory scanning and file contents copying are
    processed by usr/gen_init_cpio.

    -See also 'usr/gen_initramfs_list.sh -h'.
    +See also 'usr/gen_initramfs.sh -h'.

    Where's this all leading?
    =========================
    --- a/Documentation/filesystems/ramfs-rootfs-initramfs.rst
    +++ b/Documentation/filesystems/ramfs-rootfs-initramfs.rst
    @@ -170,7 +170,7 @@ Documentation/driver-api/early-userspace
    The kernel does not depend on external cpio tools. If you specify a
    directory instead of a configuration file, the kernel's build infrastructure
    creates a configuration file from that directory (usr/Makefile calls
    -usr/gen_initramfs_list.sh), and proceeds to package up that directory
    +usr/gen_initramfs.sh), and proceeds to package up that directory
    using the config file (by feeding it to usr/gen_init_cpio, which is created
    from usr/gen_init_cpio.c). The kernel's build-time cpio creation code is
    entirely self-contained, and the kernel's boot-time extractor is also

    \
     
     \ /
      Last update: 2021-07-26 18:44    [W:4.131 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site