From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: [PATCH] Or as we say, "cramfs"
Date: Thu, 26 Aug 2004 17:59:45 +1000 [thread overview]
Message-ID: <1093507185.29321.2513.camel@bach> (raw)
Name: Use Name cramfs in Kconfig Message
Status: Untested
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
A senior kernel hacker couldn't find the cramfs option. No wonder,
the message doesn't mention cramfs at all.
diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal .9580-linux-2.6.9-rc1-bk1/fs/Kconfig .9580-linux-2.6.9-rc1-bk1.updated/fs/Kconfig
--- .9580-linux-2.6.9-rc1-bk1/fs/Kconfig 2004-08-25 09:53:58.000000000 +1000
+++ .9580-linux-2.6.9-rc1-bk1.updated/fs/Kconfig 2004-08-26 17:56:13.000000000 +1000
@@ -1213,7 +1213,7 @@ config JFFS2_CMODE_SIZE
endchoice
config CRAMFS
- tristate "Compressed ROM file system support"
+ tristate "Compressed ROM file system support (cramfs)"
select ZLIB_INFLATE
help
Saying Y here includes support for CramFs (Compressed ROM File
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
reply other threads:[~2004-08-26 8:07 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=1093507185.29321.2513.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@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