The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>, Rabin Vincent <rabin@rab.in>
Cc: trivial@kernel.org
Subject: Re: [PATCH] doc: remove incorrect config option location
Date: Thu, 3 Jul 2008 16:06:17 -0500 (CDT)	[thread overview]
Message-ID: <29631811.1215119177276.JavaMail.oracle@acsmt302.oracle.com> (raw)
In-Reply-To: <20080703172257.GA1498@debian>


--- 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@rab.in>

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

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
> 


      reply	other threads:[~2008-07-03 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 17:22 [PATCH] doc: remove incorrect config option location Rabin Vincent
2008-07-03 21:06 ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29631811.1215119177276.JavaMail.oracle@acsmt302.oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rabin@rab.in \
    --cc=trivial@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox