All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Wookey <wookey@wookware.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: yaffs2 NAND fs
Date: Thu, 4 Mar 2010 14:43:14 +0100	[thread overview]
Message-ID: <201003041443.14780.arnd@arndb.de> (raw)
In-Reply-To: <20100304123420.GW27571@dream.aleph1.co.uk>

On Thursday 04 March 2010, Wookey wrote:
> So, I guess this is another kick. I'll update the mainline patch I
> have (which is essentially just YAFFS2 with all the "#ifdef kernel
> nnn" code taken out, and the YAFFS-direct and ecos and WinCE code
> removed, to current kernel (which also means updating balloon3 to current
> kernel so I can actually test it). I'll put that in git and ask people
> to take a look. Detailed suggestions on what extra info is needed or
> changes made would be very helpful.
> 
> Unless of course there is already concensus that this is a waste of
> time and Peter and I are the only people that want to see it in
> mainline?

The bar for getting stuff into the kernel has gotten a lot lower these
days, at least for the staging part, see
http://www.kroah.com/log/linux/linux-staging-update.html

The basic requirement would be that you can get a patch that adds
a populated drivers/staging/yaffs2 directory actually builds, ideally
even mounts existing file sytem images without crashing every time ;-)

>From there, you can do all the cleanups that are necessary to
get it moved to fs/yaffs2, including the stuff you mention above
and whatever else comes up (put it into drivers/staging/yaffs2/TODO).

	Arnd

      reply	other threads:[~2010-03-04 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02  5:05 yaffs2 NAND fs Peter Paul
2010-03-02 13:51 ` Arnd Bergmann
2010-03-03 15:09   ` Maxin John
2010-03-04  0:20     ` Mike Frysinger
2010-03-04 12:34   ` Wookey
2010-03-04 13:43     ` Arnd Bergmann [this message]

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=201003041443.14780.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wookey@wookware.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.