All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>, dwmw2@infradead.org
Cc: linux-kernel@vger.kernel.org, jffs-dev@axis.com
Subject: Re: 2.6.8-rc2-mm1
Date: Thu, 29 Jul 2004 16:36:06 +0200	[thread overview]
Message-ID: <20040729143606.GB2349@fs.tum.de> (raw)
In-Reply-To: <20040728020444.4dca7e23.akpm@osdl.org>

The following issue comes from Linus' tree:

JFFS2_COMPRESSION_OPTIONS is asked even if JFFS2_FS support isn't 
selected.

The patch below adds a dependency on JFFS2_FS to 
JFFS2_COMPRESSION_OPTIONS.

I've also added a dependency on EXPERIMENTAL which seemed to be logical 
after reading the description of this option (but even if you disagree 
with this, please add the dependency on JFFS2_FS).


Signed-off-by: Adrian Bunk <bunk@fs.tum.de>

--- linux-2.6.8-pre2-mm1/fs/Kconfig.old	2004-07-29 16:24:35.000000000 +0200
+++ linux-2.6.8-pre2-mm1/fs/Kconfig	2004-07-29 16:24:55.000000000 +0200
@@ -1088,18 +1088,19 @@
 	  including a link to the mailing list where details of the remaining
 	  work to be completed for NAND flash support can be found, see the 
 	  JFFS2 web site at <http://sources.redhat.com/jffs2>.
 
 	  Say 'N' unless you have NAND flash and you are willing to test and
 	  develop JFFS2 support for it.
 
 config JFFS2_COMPRESSION_OPTIONS
 	bool "Advanced compression options for JFFS2"
+	depends on JFFS2_FS && EXPERIMENTAL
 	default n
 	help
 	  Enabling this option allows you to explicitly choose which
 	  compression modules, if any, are enabled in JFFS2. Removing
 	  compressors and mean you cannot read existing file systems,
 	  and enabling experimental compressors can mean that you
 	  write a file system which cannot be read by a standard kernel.
 
 	  If unsure, you should _definitely_ say 'N'.

  parent reply	other threads:[~2004-07-29 15:14 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28  9:04 2.6.8-rc2-mm1 Andrew Morton
2004-07-28 16:36 ` 2.6.8-rc2-mm1 Jesse Barnes
2004-07-28 17:08 ` 2.6.8-rc2-mm1 (compile stats) John Cherry
2004-07-28 19:37 ` 2.6.8-rc2-mm1 Peter Osterlund
2004-07-28 22:24 ` 2.6.8-rc2-mm1 Johannes Stezenbach
2004-07-28 22:44   ` 2.6.8-rc2-mm1 viro
2004-07-28 23:24     ` 2.6.8-rc2-mm1 Johannes Stezenbach
2004-07-28 23:34       ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-29  0:08         ` 2.6.8-rc2-mm1 Johannes Stezenbach
2004-07-29  6:42           ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-29 19:35       ` 2.6.8-rc2-mm1 Michael Hunold
2004-07-29 21:02         ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-28 22:49 ` 2.6.8-rc2-mm1 Adam Kropelin
2004-07-28 23:20   ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-28 23:13 ` 2.6.8-rc2-mm1 Paul Jackson
2004-07-29 14:36 ` Adrian Bunk [this message]
2004-07-29 19:36   ` 2.6.8-rc2-mm1 David Woodhouse
2004-07-29 14:41 ` 2.6.8-rc2-mm1: NTFS compile error with gcc 2.95 Adrian Bunk
2004-07-29 15:54   ` Jan-Benedict Glaw
2004-07-29 20:42     ` [patch] " Adrian Bunk
     [not found]       ` <Pine.LNX.4.60.0407292249120.25661@hermes-1.csi.cam.ac.uk>
2004-07-29 23:18         ` Adrian Bunk
2004-07-29 21:27 ` 2.6.8-rc2-mm1: DVB: "errno" undefined Adrian Bunk
2004-07-29 22:44   ` Kenneth Aafløy
2004-07-29 23:24     ` Adrian Bunk
2004-07-30 14:30       ` Arnd Bergmann
2004-07-31 10:09 ` 2.6.8-rc2-mm1 breaks PPPoE for me (was: 2.6.8-rc2-mm1) Matthias Andree
2004-07-31 16:39 ` 2.6.8-rc2-mm1 Zwane Mwaikambo
2004-07-31 18:47   ` 2.6.8-rc2-mm1 Andrew Morton
2004-07-31 19:54     ` 2.6.8-rc2-mm1 Zwane Mwaikambo
2004-07-31 20:09       ` 2.6.8-rc2-mm1 Zwane Mwaikambo
2004-07-31 20:21         ` 2.6.8-rc2-mm1 Andrew Morton
2004-08-01  4:21           ` 2.6.8-rc2-mm1 Zwane Mwaikambo
2004-08-01 11:16           ` 2.6.8-rc2-mm1 Ingo Molnar
2004-08-01 11:05     ` 2.6.8-rc2-mm1 Ingo Molnar
2004-08-01  2:36 ` 2.6.8-rc2-mm1 William Lee Irwin III
2004-08-01  8:05   ` 2.6.8-rc2-mm1 Andrew Morton
2004-08-01 12:33     ` 2.6.8-rc2-mm1 William Lee Irwin III
2004-08-01 21:11       ` 2.6.8-rc2-mm1 Sam Ravnborg
2004-08-01 23:57         ` 2.6.8-rc2-mm1 William Lee Irwin III
2004-08-03 20:46           ` 2.6.8-rc2-mm1 Sam Ravnborg

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=20040729143606.GB2349@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=jffs-dev@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.