From: Theodore Tso <tytso@mit.edu>
To: Chase Venters <chase.venters@clientec.com>
Cc: bidulock@openss7.org, Daniel Phillips <phillips@google.com>,
Stephen Hemminger <shemminger@osdl.org>,
Sridhar Samudrala <sri@us.ibm.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] in-kernel sockets API
Date: Wed, 14 Jun 2006 06:36:05 -0400 [thread overview]
Message-ID: <20060614103605.GA17831@thunk.org> (raw)
In-Reply-To: <200606131953.42002.chase.venters@clientec.com>
On Tue, Jun 13, 2006 at 07:53:19PM -0500, Chase Venters wrote:
> > It is the lack of an ABI that is most frustrating to these users.
>
> And the presence of an ABI would be _very_ frustrating to core
> developers. Not only would these people suffer, everyone would --
> developer time would be wasted dealing with cruft, and forward
> progress would be slowed.
Note that just because an interface is EXPORT_SYMBOL doesn't mean that
the interface is guaranteed to be stable. So folks who are aruging
that an interface shouldn't be usable by non-GPL applications because
we are therefore guaranteeing a stable API are making an unwarranted
assumption.
- Ted
next prev parent reply other threads:[~2006-06-14 10:36 UTC|newest]
Thread overview: 34+ 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 ` 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 [this message]
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 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=20060614103605.GA17831@thunk.org \
--to=tytso@mit.edu \
--cc=bidulock@openss7.org \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=phillips@google.com \
--cc=shemminger@osdl.org \
--cc=sri@us.ibm.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).