All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: ian@brightstareng.com
Cc: linux-mtd@lists.infradead.org
Subject: RE: JFFS2 Support for Large Flash Designs
Date: Wed, 07 Mar 2007 19:37:14 +0100	[thread overview]
Message-ID: <1173292634.24738.663.camel@localhost.localdomain> (raw)
In-Reply-To: <200703071317.38907.ian@brightstareng.com>

On Wed, 2007-03-07 at 13:17 -0500, ian@brightstareng.com wrote:
> On Wednesday 07 March 2007 12:48, Thomas Gleixner wrote:
> > SoC devices out of tree are a seperate steaming pile of ... I
> > have seen too many chip vendor kernels explode when you just
> > try to do anything else than run "hello world" on them.
> 
> I agree that this is far from ideal -- I have to deal with this 
> all the time.  But I also appreciate that some vendors do 
> actually bother to contribute some base code to support their 
> designs, even if I have to go in and fix it.
> 
> The vendors need to do better job at establishing a framework to 
> solicit fixes, improvements and new code from their customers, 
> integrate it, and feed it up the tree into the mainline. It is 
> clearly to their benefit.

As well as it would be for out of tree drivers and such. The time people
spend to catch up with mainline to maintain their #ifdef mess would be
much more useful spent when the stuff would be in tree.

	tglx

  reply	other threads:[~2007-03-07 18:31 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 [this message]
2007-03-07 18:07   ` Jörn Engel
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=1173292634.24738.663.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --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.