mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: frans <fransmeulenbroeks@gmail.com>
To: mtk.manpages@gmail.com, rdunlap@xenotime.net,
	linux-doc@vger.kernel.org, torvalds@linux-foundation.org
Cc: trivial@kernel.org, rob@landley.net, linux-kernel@vger.kernel.org
Subject: [TRIVIAL] [PATCH] Documentation/filesystems/ramfs-rootfs-initramfs.txt
Date: Sat, 22 Nov 2008 15:39:06 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0811221532020.14306@frans-desktop> (raw)

A very minor patch on ramfs-rootfs-initramfs.txt.
update the location where CONFIG_INITRAMFS_SOURCE lives in menuconfig

diff --git a/Documentation/filesystems/ramfs-rootfs-initramfs.txt b/Documentation/filesystems/ramfs-rootfs-initramfs.txt
index 62fe9b1..a8273d5 100644
--- a/Documentation/filesystems/ramfs-rootfs-initramfs.txt
+++ b/Documentation/filesystems/ramfs-rootfs-initramfs.txt
@@ -130,12 +130,12 @@ 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 (in General Setup 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:

   dir /dev 755 0 0
   nod /dev/console 644 0 0 c 5 1

Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>

             reply	other threads:[~2008-11-22 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 14:39 frans [this message]
2008-11-23  0:44 ` Rob Landley
  -- strict thread matches above, loose matches on Subject: below --
2008-08-17  9:07 frans
2008-08-20  5:56 ` Rob Landley

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=alpine.DEB.1.00.0811221532020.14306@frans-desktop \
    --to=fransmeulenbroeks@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=rdunlap@xenotime.net \
    --cc=rob@landley.net \
    --cc=torvalds@linux-foundation.org \
    --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

all inboxes | Powered by JetHome®