From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Chase Venters <chase.venters@clientec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] in-kernel sockets API
Date: Wed, 14 Jun 2006 00:54:18 -0400 [thread overview]
Message-ID: <448F967A.8070801@ens-lyon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606131655580.4856@turbotaz.ourhouse>
Chase Venters wrote:
> At least some of us feel like stable module APIs should be explicitly
> discouraged, because we don't want to offer comfort for code that
> refuses to live in the tree (since getting said code into the tree is
> often a goal).
>
> I'm curious now too - can you name some non-GPL non-proprietary
> modules we should be concerned about? I'd think most of the possible
> examples (not sure what they are) would be better off dual-licensed
> (one license being GPL) and in-kernel.
What about GPL modules that don't want to get merged ? I don't know any
such module that could use this API. But at least there are some webcam
drivers that don't seem to want to be merged (I don't know why).
I agree with making life hard for proprietary modules. I agree that
maintaining a stable API is hard. But I don't see the actual point of
discouraging modules to stay out of tree.
Brice
next prev parent reply other threads:[~2006-06-14 4:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 23:56 [RFC/PATCH 1/2] in-kernel sockets API Sridhar Samudrala
2006-06-13 5:07 ` Stephen Hemminger
2006-06-13 11:13 ` Arnaldo Carvalho de Melo
2006-06-13 11:22 ` Brian F. G. Bidulock
2006-06-13 21:12 ` Daniel Phillips
2006-06-13 21:40 ` Brian F. G. Bidulock
2006-06-13 22:00 ` Chase Venters
2006-06-13 22:30 ` Daniel Phillips
2006-06-13 22:47 ` Brian F. G. Bidulock
2006-06-13 23:59 ` H. Peter Anvin
2006-06-13 23:59 ` Chase Venters
2006-06-13 23:59 ` Chase Venters
2006-06-14 0:31 ` Brian F. G. Bidulock
2006-06-14 0:53 ` Chase Venters
2006-06-14 6:07 ` Brian F. G. Bidulock
2006-06-14 7:58 ` Chase Venters
2006-06-14 9:28 ` Brian F. G. Bidulock
2006-06-14 10:43 ` Alan Cox
2006-06-14 10:54 ` Brian F. G. Bidulock
2006-06-14 10:36 ` Theodore Tso
2006-06-14 6:28 ` David Schwartz
2006-06-13 22:44 ` Brian F. G. Bidulock
2006-06-13 23:42 ` Ben Greear
2006-06-14 0:05 ` Chase Venters
2006-06-14 0:18 ` Brian F. G. Bidulock
2006-06-14 0:29 ` Chase Venters
2006-06-14 0:36 ` Brian F. G. Bidulock
2006-06-14 0:19 ` Ben Greear
2006-06-14 0:38 ` Brian F. G. Bidulock
2006-06-14 0:07 ` H. Peter Anvin
2006-06-14 4:54 ` Brice Goglin [this message]
2006-06-14 5:03 ` Dave Jones
2006-06-14 5:28 ` Chris Friesen
2006-06-14 13:30 ` Harald Welte
2006-06-14 14:29 ` Erik Mouw
2006-06-14 15:26 ` Harald Welte
2006-06-14 17:48 ` Daniel Phillips
2006-06-14 18:03 ` Brian F. G. Bidulock
2006-06-14 20:52 ` Sridhar Samudrala
2006-06-13 14:58 ` Jan Engelhardt
2006-06-13 16:27 ` Sridhar Samudrala
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=448F967A.8070801@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@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 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.