linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: vb <vb@vsbe.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Linux Embedded Maillist <linux-embedded@vger.kernel.org>, corbet@lwn.net
Subject: Re: Adding a new platform
Date: Wed, 20 Aug 2008 08:39:17 -0700	[thread overview]
Message-ID: <f608b67d0808200839l2b41f0fejbf813a5dbc6e9fc4@mail.gmail.com> (raw)
In-Reply-To: <20080820101044.5df8b7d8@hskinnemo-gx745.norway.atmel.com>

On Wed, Aug 20, 2008 at 1:10 AM, Haavard Skinnemoen
<haavard.skinnemoen@atmel.com> wrote:
> vb <vb@vsbe.com> wrote:
>> Would such a driver be accepted? Wouldn't such a driver get stale
>> after a few kernel releases?
>
> Yes, the kernel contains tons of such platform-specific drivers. No, it
> won't get stale as long as someone who has access to the hardware is
> willing to test a -rc kernel every once in a while.
>
> You can't really expect to get away with no maintenance at all, but in
> my experience, it takes much less effort to maintain a driver in-tree
> than out-of-tree. It's also much easier to get help if it's in-tree.
>

fair enough, maybe this paragraph should be added to the original document.

cheers,
/v

> Haavard
>

  reply	other threads:[~2008-08-20 15:39 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 [this message]
2008-08-21  3:02         ` Charles Manning
2008-08-21  8:40           ` David Woodhouse
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=f608b67d0808200839l2b41f0fejbf813a5dbc6e9fc4@mail.gmail.com \
    --to=vb@vsbe.com \
    --cc=corbet@lwn.net \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=linux-embedded@vger.kernel.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 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).