From: Kinglong Mee <kinglongmee@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: [PATCH] Documentation/early-userspace/README fix a bad description
Date: Mon, 02 Mar 2015 19:28:32 +0800 [thread overview]
Message-ID: <54F44960.300@gmail.com> (raw)
Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
---
Documentation/early-userspace/README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/early-userspace/README b/Documentation/early-userspace/README
index 93e63a9..ed07371 100644
--- a/Documentation/early-userspace/README
+++ b/Documentation/early-userspace/README
@@ -70,7 +70,7 @@ scripts/gen_initramfs_list.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
the contents are scanned, uid/gid translation is performed, and
-usr/gen_init_cpio file directives are output. If a directory is
+usr/gen_init_cpio file directives are output. If a file is
specified as an argument to scripts/gen_initramfs_list.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
--
2.1.0
reply other threads:[~2015-03-02 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54F44960.300@gmail.com \
--to=kinglongmee@gmail.com \
--cc=linux-fsdevel@vger.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;
as well as URLs for NNTP newsgroup(s).