From: Andreas Dilger <adilger@clusterfs.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Jeff Garzik <jeff@garzik.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, jffs-dev@axis.com,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH/RFC] Delete JFFS (version 1)
Date: Tue, 12 Dec 2006 14:49:04 -0700 [thread overview]
Message-ID: <20061212214904.GR5937@schatzie.adilger.int> (raw)
In-Reply-To: <625fc13d0612121038l22a2b252v3d3773caa8826e41@mail.gmail.com>
On Dec 12, 2006 12:38 -0600, Josh Boyer wrote:
> On 12/12/06, Andrew Morton <akpm@osdl.org> wrote:
> >It would be good to provide unignorable notice of this in 2.6.20. Via a
> >loud printk, or perhaps even CONFIG_BROKEN or CONFIG_EMBEDDED.
>
> Something like the below?
>
> Make CONFIG_JFFS depend on CONFIG_BROKEN
>
> Signed-off-by: Josh Boyer <jwboyer@gmail.com>
>
> diff --git a/fs/Kconfig b/fs/Kconfig
> index b3b5aa0..4ac367d 100644
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -1204,13 +1204,16 @@ config EFS_FS
>
> config JFFS_FS
> tristate "Journalling Flash File System (JFFS) support"
> - depends on MTD && BLOCK
> + depends on MTD && BLOCK && BROKEN
> help
> JFFS is the Journalling Flash File System developed by Axis
> Communications in Sweden, aimed at providing a crash/powerdown-safe
> file system for disk-less embedded devices. Further information is
> available at (<http://developer.axis.com/software/jffs/>).
>
> + NOTE: This filesystem is deprecated and is scheduled for removal in
> + 2.6.21. See Documentation/feature-removal-schedule.txt
> +
It would be better to have a printk in the module init, since users with
upstream builds won't see the config help.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-12-12 21:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 12:39 Jeff Garzik
2006-12-12 12:56 ` Josh Boyer
2006-12-12 13:02 ` Jeff Garzik
2006-12-12 13:06 ` Josh Boyer
2006-12-12 13:07 ` David Woodhouse
2006-12-12 13:09 ` Jeff Garzik
2006-12-12 17:01 ` Bill Nottingham
2006-12-12 17:20 ` Jeff Garzik
2006-12-12 17:28 ` Alan
2006-12-19 10:56 ` David Weinehall
2006-12-12 12:58 ` Jörn Engel
2006-12-12 17:53 ` Andrew Morton
2006-12-12 18:38 ` Josh Boyer
2006-12-12 21:49 ` Andreas Dilger [this message]
2006-12-13 7:06 ` Jörn Engel
2007-03-09 23:13 ` Stefan Monnier
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=20061212214904.GR5937@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=jeff@garzik.org \
--cc=jffs-dev@axis.com \
--cc=jwboyer@gmail.com \
--cc=linux-fsdevel@vger.kernel.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
all inboxes | Powered by JetHome®