All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@lazybastard.org>
To: ian@brightstareng.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Support for Large Flash Designs
Date: Wed, 7 Mar 2007 19:07:47 +0100	[thread overview]
Message-ID: <20070307180743.GC16439@lazybastard.org> (raw)
In-Reply-To: <200703071223.07485.ian@brightstareng.com>

Please keep me on the Cc: list.

On Wed, 7 March 2007 12:23:07 -0500, ian@brightstareng.com wrote:
> 
> There are some positives of having components maintained outside 
> the context of "linux".

Can you name those?

> Yaffs actually has a life outside linux.  Using "outside the 
> mainline" as an argument is weak at best. The 2.6 kernel 
> makefile makes building a module outside the tree trivial -- so 
> lots of the older build hassles and arguments no longer exist.

If building it were our only problem...

Problems that cause much more trouble are:
o Following the changing in-kernel APIs.  I maintain several
  out-of-tree projects myself and can tell you it is a pain.  At times I
  don't update my kernel for month because I lack the time to update the
  cowlink patches.
o Problem support.  Unless the code is in mainline, the only person that
  will be willing to assist a user is the one responsible for the
  out-of-tree project.  Such support can be good, on average it tends to
  be somewhat worse.
o Code maturity.  Face it, there is often a reason why the code is not
  in mainline.

How much of the above applies to YAFFS is a seperate question I don't
want to answer.  But in general, being wary of out-of-tree code is a
good thing.

Jörn

-- 
"Error protection by error detection and correction."
-- from a university class

  parent reply	other threads:[~2007-03-07 18:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.311.1173272465.2275.linux-mtd@lists.infradead.org>
2007-03-07 17:23 ` JFFS2 Support for Large Flash Designs ian
2007-03-07 17:48   ` Thomas Gleixner
2007-03-07 17:54     ` Lennert Buytenhek
2007-03-07 18:17     ` ian
2007-03-07 18:37       ` Thomas Gleixner
2007-03-07 18:07   ` Jörn Engel [this message]
2007-03-06 21:34 Johnson, Charles F
2007-03-07  1:36 ` Josh Boyer
2007-03-07  1:38   ` Johnson, Charles F
2007-03-07  1:47     ` Josh Boyer
2007-03-07 11:04     ` Jörn Engel
2007-03-07  6:47 ` Vitaly Wool
2007-03-07  7:09   ` Charles Manning

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=20070307180743.GC16439@lazybastard.org \
    --to=joern@lazybastard.org \
    --cc=ian@brightstareng.com \
    --cc=linux-mtd@lists.infradead.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.