[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101028174432.GA2001@kroah.com>
Date: Thu, 28 Oct 2010 10:44:32 -0700
From: Greg KH <greg@...ah.com>
To: Charles Manning <manningc2@...rix.gen.nz>
Cc: Randy Dunlap <randy.dunlap@...cle.com>,
linux-kernel@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: How do I add yaffs file system to mainline?
On Thu, Oct 28, 2010 at 10:26:41AM -0700, Randy Dunlap wrote:
> On Fri, 29 Oct 2010 04:55:02 +1300 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/
>
> It's difficult to review & comment on a git tree.
> We prefer patches via email for review.
>
> > 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?
>
> Either ask Stephen Rothwell to add the git tree to the linux-next daily tree
> or ask Greg KH to add it to the drivers/staging/ area.
I'd be glad to add the code to the staging tree, but to do so, do you
have a list of things that are left to do in order to get it properly
merged to the "real" portion of the kernel?
And if so, what is preventing you from doing those tasks right now to
get the code into the .38 kernel merge?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists