From: Mike Frysinger <vapier.adi@gmail.com>
To: Maxin John <maxin.john@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Peter Paul <abnominales@web.de>,
linux-kernel@vger.kernel.org
Subject: Re: yaffs2 NAND fs
Date: Wed, 3 Mar 2010 19:20:37 -0500 [thread overview]
Message-ID: <8bd0f97a1003031620s44cff658x81fc36fa2a8efd96@mail.gmail.com> (raw)
In-Reply-To: <9debc4411003030709r597d4f6dmeacadce5c3cf2ed7@mail.gmail.com>
On Wed, Mar 3, 2010 at 10:09, Maxin John wrote:
> On Tue, Mar 2, 2010 at 7:21 PM, Arnd Bergmann wrote:
>> On Tuesday 02 March 2010, Peter Paul wrote:
>>> I was wondering why the yaffs2 file system has not gone for mainline
>>> yet. It's rather popular flash file system in the embedded world, while
>>> it is rather easy to patch a kernel to have yaffs2 support [1] it would
>>> be even nicer if it was just in mainline.
>>> The source of the GPLv2 file system can be found at [2]
>>>
>>> [1] http://www.yaffs.net/howto-incorporate-yaffs
>>> [2] http://www.aleph1.co.uk/cgi-bin/viewcvs.cgi/yaffs2/
>>
>> I would guess it's a combination of multiple reasons:
>>
>> 1. It has not been submitted for upstream inclusion, at least not
>> during the last few years.
>> 2. We don't have a staging area like drivers/staging for file systems
>> in the way that we have for drivers
>> 3. There is now ubifs and (soon) logfs upstream, both of which appear
>> to be superior to yaffs in many ways.
>
> This means there should be no reference to YAFFS2 in the upstream
> kernel? Because, I have located some defconfigs in upstream kernel
> where YAFFS2 support is enabled by default.
irrelevant noise
-mike
next prev parent reply other threads:[~2010-03-04 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 5:05 Peter Paul
2010-03-02 13:51 ` Arnd Bergmann
2010-03-03 15:09 ` Maxin John
2010-03-04 0:20 ` Mike Frysinger [this message]
2010-03-04 12:34 ` Wookey
2010-03-04 13:43 ` Arnd Bergmann
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=8bd0f97a1003031620s44cff658x81fc36fa2a8efd96@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=abnominales@web.de \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maxin.john@gmail.com \
/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®