linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Charles Manning <manningc2@actrix.gen.nz>
Cc: vb <vb@vsbe.com>, Paul Gortmaker <paul.gortmaker@gmail.com>,
	Linux Embedded Maillist <linux-embedded@vger.kernel.org>,
	corbet@lwn.net
Subject: Re: Adding a new platform
Date: Thu, 21 Aug 2008 09:40:39 +0100	[thread overview]
Message-ID: <1219308039.2988.242.camel@pmac.infradead.org> (raw)
In-Reply-To: <200808211502.58206.manningc2@actrix.gen.nz>

On Thu, 2008-08-21 at 15:02 +1200, Charles Manning wrote:
> 
> In-tree is no silver bullet.
> 
> When people modify internal APIs they will likely fix anything that breaks 
> compilation. However many things are more subtle than that and it is very 
> easy to end up with a driver or other code that compiles but does not work 
> properly.
> 
> Luckily APIs for drivers (the most common stuff that people work on) don't 
> change that much, and the interfaces are reasonably clear. If you want some 
> hell then try working on file systems :-).

File systems show an excellent example of why you're wrong, in fact. The
API for file systems changes quite a lot, and the people who make those
changes do tend to fix up all the in-tree file systems simultaneously,
-- and since they're doing it with a full understanding of the
implications of the change they're making, they usually manage to get
the change _right_.

I find it's more common to introduce subtle errors when the person
modifying the core API _hasn't_ also modified the driver/fs code which
uses that API. Which is what happens when you have out-of-tree code.

I'd rather remove my gonads with a rusty spoon than maintain an
out-of-tree file system.

-- 
dwmw2

  reply	other threads:[~2008-08-21  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 18:01 Adding a new platform David VomLehn
2008-08-19 18:22 ` Ralf Baechle
2008-08-20  3:19 ` Paul Gortmaker
2008-08-20  3:57   ` vb
2008-08-20  4:29     ` Paul Gortmaker
2008-08-20  5:15       ` vb
2008-08-20  8:10         ` Haavard Skinnemoen
2008-08-20 15:39           ` vb
2008-08-21  3:02         ` Charles Manning
2008-08-21  8:40           ` David Woodhouse [this message]
2008-08-21  8:46           ` Geert Uytterhoeven
2008-08-21  8:48             ` David Woodhouse
2008-08-22  4:53             ` Phillip Lougher
2008-08-22  7:25               ` Peter Korsgaard
2008-08-20  4:44     ` Paul Mundt

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=1219308039.2988.242.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-embedded@vger.kernel.org \
    --cc=manningc2@actrix.gen.nz \
    --cc=paul.gortmaker@gmail.com \
    --cc=vb@vsbe.com \
    /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).