From: vb <vb@vsbe.com>
To: Paul Gortmaker <paul.gortmaker@gmail.com>
Cc: Linux Embedded Maillist <linux-embedded@vger.kernel.org>, corbet@lwn.net
Subject: Re: Adding a new platform
Date: Tue, 19 Aug 2008 22:15:01 -0700 [thread overview]
Message-ID: <f608b67d0808192215q5b8ffbf0w70531c31cdd66bcd@mail.gmail.com> (raw)
In-Reply-To: <7d1d9c250808192129j3fb7ef28p8f404c6affd82078@mail.gmail.com>
On Tue, Aug 19, 2008 at 9:29 PM, Paul Gortmaker
<paul.gortmaker@gmail.com> wrote:
> On Tue, Aug 19, 2008 at 11:57 PM, vb <vb@vsbe.com> wrote:
>>
>> so, say a developer submits a proprietary driver and it gets accepted.
>
> Doesn't happen. By design. If the driver is proprietary then it is presumably
> not meant for open distribution, and hence not compatible with GPL and
> widespread distribution into 100,000 public git repositories. So it won't
> get submitted and it won't get accepted.
>
I guess 'proprietary' is not the right term then, how do you call a
driver which is not a secret and not a problem to release, but
controls some hardware present in only in certain devices of a certain
company.
Would such a driver be accepted? Wouldn't such a driver get stale
after a few kernel releases?
next prev parent reply other threads:[~2008-08-20 5:15 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 [this message]
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
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=f608b67d0808192215q5b8ffbf0w70531c31cdd66bcd@mail.gmail.com \
--to=vb@vsbe.com \
--cc=corbet@lwn.net \
--cc=linux-embedded@vger.kernel.org \
--cc=paul.gortmaker@gmail.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).