From: Scott A McConnell <samcconn@cotw.com>
To: linux-kernel@vger.kernel.org
Subject: fs/Config.in :Simple patch to require CONFIG_PROC_FS before CONFIG_JFFS_PROC_FS is available.
Date: Fri, 01 Mar 2002 14:52:26 -0600 [thread overview]
Message-ID: <3C7FEA0A.250D71DB@cotw.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
--- fs/Config.in.old Fri Mar 1 11:33:18 2002
+++ fs/Config.in Fri Mar 1 11:33:25 2002
@@ -37,7 +37,7 @@
dep_tristate 'Journalling Flash File System (JFFS) support'
CONFIG_JFFS_FS $CONFIG_MTD
if [ "$CONFIG_JFFS_FS" = "y" -o "$CONFIG_JFFS_FS" = "m" ] ; then
int 'JFFS debugging verbosity (0 = quiet, 3 = noisy)'
CONFIG_JFFS_FS_VERBOSE 0
- bool 'JFFS stats available in /proc filesystem' CONFIG_JFFS_PROC_FS
+ dep_mbool 'JFFS stats available in /proc filesystem'
CONFIG_JFFS_PROC_FS $CONFIG_PROC_FS
fi
dep_tristate 'Journalling Flash File System v2 (JFFS2) support'
CONFIG_JFFS2_FS $CONFIG_MTD
if [ "$CONFIG_JFFS2_FS" = "y" -o "$CONFIG_JFFS2_FS" = "m" ] ; then
--
Scott A. McConnell
[-- Attachment #2: Config.in.patch --]
[-- Type: text/plain, Size: 673 bytes --]
--- fs/Config.in.old Fri Mar 1 11:33:18 2002
+++ fs/Config.in Fri Mar 1 11:33:25 2002
@@ -37,7 +37,7 @@
dep_tristate 'Journalling Flash File System (JFFS) support' CONFIG_JFFS_FS $CONFIG_MTD
if [ "$CONFIG_JFFS_FS" = "y" -o "$CONFIG_JFFS_FS" = "m" ] ; then
int 'JFFS debugging verbosity (0 = quiet, 3 = noisy)' CONFIG_JFFS_FS_VERBOSE 0
- bool 'JFFS stats available in /proc filesystem' CONFIG_JFFS_PROC_FS
+ dep_mbool 'JFFS stats available in /proc filesystem' CONFIG_JFFS_PROC_FS $CONFIG_PROC_FS
fi
dep_tristate 'Journalling Flash File System v2 (JFFS2) support' CONFIG_JFFS2_FS $CONFIG_MTD
if [ "$CONFIG_JFFS2_FS" = "y" -o "$CONFIG_JFFS2_FS" = "m" ] ; then
next reply other threads:[~2002-03-01 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 20:52 Scott A McConnell [this message]
2002-03-02 15:45 ` fs/Config.in :Simple patch to require CONFIG_PROC_FS before CONFIG_JFFS_PROC_FS is available David Woodhouse
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=3C7FEA0A.250D71DB@cotw.com \
--to=samcconn@cotw.com \
--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