linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corey Ashford <cjashfor@linux.vnet.ibm.com>
To: Charles Manning <manningc2@actrix.gen.nz>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: How do I add yaffs file system to mainline?
Date: Thu, 28 Oct 2010 10:58:01 -0700	[thread overview]
Message-ID: <4CC9B9A9.20904@linux.vnet.ibm.com> (raw)
In-Reply-To: <201010281308.16774.manningc2@actrix.gen.nz>

On 10/27/2010 05:08 PM, Charles Manning wrote:
> YAFFS has been used for many years as a third-party patch-in.
>
> I have recently been through the exercise of changing all the symbols to be
> more kernel friendly with the intention of mainlining into the linux tree.
>
> The code is in git at http://github.com/cdhmanning/linux-yaffs-integration/
>
> Thanks to CELF and Google for sponsoring the effort so far.
>
> What still needs to be done to mainline this?
> Who do I need to approach?

I'd say you need to post a series of incremental patches which 
introduces this filesystem, why the kernel should have it, why people 
would want it, etc.

For lots more details, you should take a look at the files in 
Documentation/development-process in the kernel source tree.

-- 
Regards,

- Corey

Corey Ashford
Software Engineer
IBM Linux Technology Center, Linux Toolchain
Beaverton, OR
cjashfor@us.ibm.com

  reply	other threads:[~2010-10-28 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28  0:08 How do I add yaffs file system to mainline? Charles Manning
2010-10-28 17:58 ` Corey Ashford [this message]
     [not found] <201010290455.02390.manningc2@actrix.gen.nz>
     [not found] ` <20101028102641.d936aec8.randy.dunlap@oracle.com>
     [not found]   ` <201010290641.13820.manningc2@actrix.gen.nz>
     [not found]     ` <20101028174932.GB2205@kroah.com>
2010-10-28 18:15       ` David Daney
2010-10-28 18:23         ` Greg KH

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=4CC9B9A9.20904@linux.vnet.ibm.com \
    --to=cjashfor@linux.vnet.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manningc2@actrix.gen.nz \
    /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;
as well as URLs for NNTP newsgroup(s).