From: "Chris Friesen" <cfriesen@nortel.com>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: Chase Venters <chase.venters@clientec.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] in-kernel sockets API
Date: Tue, 13 Jun 2006 23:28:42 -0600 [thread overview]
Message-ID: <448F9E8A.1070608@nortel.com> (raw)
In-Reply-To: <448F967A.8070801@ens-lyon.org>
Brice Goglin wrote:
> 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).
There are valid reasons for GPL code to not be merged into mainline.
I (and I'm sure there are others) work on GPL modules/patches that have
no hope of making it into mainline because they're too specialized.
Custom netfilter modules, drivers for special hardware, scheduler
changes, additional instrumentation, etc.
Plus, we're usually working on a stabilized older version, so it's a lot
of extra work to regenerate it against current versions to even try and
merge it.
The source all goes to the customer but it just wouldn't make sense to
have it in mainline.
So the "churn mainline to punish out-of-tree code" argument doesn't make
sense to me. If there's a good reason for the change, then go for
it--but change just to make it hard for out of tree code is simply annoying.
Chris
next prev parent reply other threads:[~2006-06-14 5:28 UTC|newest]
Thread overview: 40+ 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-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
2006-06-14 5:03 ` Dave Jones
2006-06-14 5:28 ` Chris Friesen [this message]
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=448F9E8A.1070608@nortel.com \
--to=cfriesen@nortel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox