Re: [PATCH] doc: remove incorrect config option location

[Randy Dunlap]

--- Original Message ---
> CONFIG_INITRAMFS_SOURCE is no longer under Devices->Block
> Devices, but
> is now in General Setup.  The correct location is easily found
> using menuconfig's search, so remove the mention of the incorrect
> location from the docs.
> 
> Signed-off-by: Rabin Vincent <rabin@xxxxxx>

Acked-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>

Thanks.

> ---
>  .../filesystems/ramfs-rootfs-initramfs.txt         |   11
> +++++------
>  1 files changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/Documentation/filesystems/ramfs-rootfs-initramfs.txt
> b/Documentation/filesystems/ramfs-rootfs-initramfs.txt
> index 7be232b..08547cf 100644
> --- a/Documentation/filesystems/ramfs-rootfs-initramfs.txt
> +++ b/Documentation/filesystems/ramfs-rootfs-initramfs.txt
> @@ -130,12 +130,11 @@ The 2.6 kernel build process always
> creates a gzipped cpio format initramfs
>  archive and links it into the resulting kernel binary.  By
> default, this
>  archive is empty (consuming 134 bytes on x86).
>  
> -The config option CONFIG_INITRAMFS_SOURCE (for some reason
> buried under
> -devices->block devices in menuconfig, and living in usr/Kconfig)
> can be used
> -to specify a source for the initramfs archive, which will
> automatically be
> -incorporated into the resulting binary.  This option can point
> to an existing
> -gzipped cpio archive, a directory containing files to be
> archived, or a text
> -file specification such as the following example:
> +The config option CONFIG_INITRAMFS_SOURCE can be used to
> specify a source for
> +the initramfs archive, which will automatically be incorporated
> into the
> +resulting binary.  This option can point to an existing gzipped
> cpio archive, a
> +directory containing files to be archived, or a text file
> specification such as
> +the following example:
>  
>    dir /dev 755 0 0
>    nod /dev/console 644 0 0 c 5 1
> -- 
> 1.5.6
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/