From: Ryan Mallon <ryan@bluewatersys.com>
To: Greg KH <greg@kroah.com>
Cc: Charles Manning <manningc2@actrix.gen.nz>,
cdhmanning@gmail.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/9] Add yaffs Kconfig and Makefile
Date: Fri, 05 Nov 2010 13:14:05 +1300 [thread overview]
Message-ID: <4CD34C4D.5070609@bluewatersys.com> (raw)
In-Reply-To: <20101104223641.GA3596@kroah.com>
On 11/05/2010 11:36 AM, Greg KH wrote:
> On Fri, Nov 05, 2010 at 09:58:38AM +1300, Charles Manning wrote:
>> On Thursday 04 November 2010 06:46:07 Greg KH wrote:
>>> On Thu, Nov 04, 2010 at 05:53:16AM +1300, cdhmanning@gmail.com wrote:
>>>> From: Charles Manning <cdhmanning@gmail.com>
>>>>
>>>> Adding yaffs2 file system.
>>>>
>>>> Signed-off-by: Charles Manning <cdhmanning@gmail.com>
>>>> ---
>>> Also, is your goal to get this cleaned up good enough to get it into .38
>>> in the "real" place in the kernel, or do you want to see it go through
>>> staging and take a bit longer to get everything cleaned up properly
>>> before moving to the "real" location?
>>
>> My goal it to get this into mainline, .38 preferred.
>>
>> I am a complete newbie when it comes to this process. What's the best
>> path to getting there?
>
> I don't know, both will work.
>
>> My preference is to keep cleaning up code in yaffs.net and patching
>> from there as this will keep the trees closer together and minimise
>> clerical issues.
>
> Sure, but remember, once the code goes into mainline, having an external
> tree is a huge liability, not a benifit at all, so consider dropping it.
The Yaffs codebase also runs on other operating systems. Charles has
cleaned the code up to match the Linux coding style and removed the
support for other operating systems in the patches which he is
attempting to push to mainline.
I believe his intention is to maintain his own, portable, yaffs codebase
which supports Linux and other systems out of tree. There will be some
work for Charles in keeping these two codebases in sync, but that won't
have any visible effect to Linux.
The trick for Charles is to make the Yaffs code which he is submitting
for mainline inclusion clean according to the Linux coding standards,
without creating a maintainence nightmare for himself :-).
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan@bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2010-11-05 0:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 16:53 [PATCH 0/9] Add yaffs2 file system cdhmanning
2010-11-03 16:53 ` [PATCH 1/9] Add yaffs Kconfig and Makefile cdhmanning
2010-11-03 17:46 ` Greg KH
2010-11-03 17:55 ` David Daney
2010-11-03 18:06 ` Greg KH
2010-11-04 20:58 ` Charles Manning
2010-11-04 22:36 ` Greg KH
2010-11-05 0:14 ` Ryan Mallon [this message]
2010-11-06 1:50 ` Valdis.Kletnieks
2010-11-07 20:59 ` Charles Manning
2010-11-07 21:45 ` Chris Snook
2010-11-07 22:22 ` Charles Manning
2010-11-08 10:24 ` Chris Snook
2010-11-08 21:22 ` Charles Manning
2010-11-08 22:15 ` Chris Snook
2010-11-03 16:53 ` [PATCH 2/9] Add yaffs allocator, bitmap and attrib source cdhmanning
2010-11-04 23:01 ` Jesper Juhl
2010-11-07 22:42 ` Charles Manning
2010-11-03 16:53 ` [PATCH 3/9] Add yaffs checkpointing, blockinfo, nameval and os context cdhmanning
2010-11-03 16:53 ` [PATCH 4/9] Add yaffs ecc, mtd access and nand abstraction code cdhmanning
2010-11-03 17:05 ` David Daney
2010-11-03 16:53 ` [PATCH 5/9] Add yaffs_guts.c cdhmanning
2010-11-03 16:53 ` [PATCH 6/9] Add some yaffs include files cdhmanning
2010-11-03 17:10 ` David Daney
2010-11-03 17:16 ` Charles Manning
2010-11-09 17:12 ` Arnd Bergmann
2010-11-03 16:53 ` [PATCH 7/9] Add yaffs tag access code cdhmanning
2010-11-03 17:16 ` David Daney
2010-11-03 17:17 ` Paulo Marques
2010-11-03 16:53 ` [PATCH 8/9] Add yaffs verification and version specific code cdhmanning
2010-11-03 16:53 ` [PATCH 9/9] Add yaffs kernel glue cdhmanning
2010-11-09 16:57 ` 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=4CD34C4D.5070609@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=cdhmanning@gmail.com \
--cc=greg@kroah.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