From: Adrian Bunk <bunk@stusta.de>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
jffs-dev@axis.com, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Make JFFS depend on CONFIG_BROKEN
Date: Sat, 30 Dec 2006 22:37:49 +0100 [thread overview]
Message-ID: <20061230213749.GE20714@stusta.de> (raw)
In-Reply-To: <625fc13d0612180525m500fcecdta08edebb3dd526a6@mail.gmail.com>
On Mon, Dec 18, 2006 at 07:25:56AM -0600, Josh Boyer wrote:
> Mark JFFS as broken and provide a warning to users that it is
> deprecated and scheduled for removal in 2.6.21
>
> 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
>...
$ grep -i jffs Documentation/feature-removal-schedule.txt
$
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-12-30 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 13:25 [PATCH] Make JFFS depend on CONFIG_BROKEN Josh Boyer
2006-12-30 21:37 ` Adrian Bunk [this message]
2007-01-01 4:32 ` Josh Boyer
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=20061230213749.GE20714@stusta.de \
--to=bunk@stusta.de \
--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 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.