All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification
Date: Wed, 02 Apr 2008 15:50:21 +0000	[thread overview]
Message-ID: <47F3AB3D.7050906@hp.com> (raw)
In-Reply-To: <47F2AD4E.8000203@hp.com>

Hi Ivan

Ivan Skytte Jørgensen wrote:
> 
> 
> And while we are at it: please reread my message from 2006-12-27 about some 
> thoughtsI had about sctp_connectx(). I have still not had any time to do 
> anything about it :-/
> 
> /isj
> 

I've been pondering the library change as well and the conclusion I've 
come to is that we either introduce some ugliness into the 
include/net/sctp.h or we break the API and force people to recompile.

This is really a result of breaking the API in the specification.  That
should not have been allowed, but we now have to live with it.

The good thing is the lksctp library has been unofficially tied to the 
kernel for some time; however, we haven't had to deal with such blatant
API breakage yet.

-vlad

  parent reply	other threads:[~2008-04-02 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 21:46 [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification Vlad Yasevich
2008-04-01 22:42 ` [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification of sctp Ivan Skytte Jørgensen
2008-04-02 15:50 ` Vlad Yasevich [this message]
2008-04-11 19:56 ` [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification Vlad Yasevich
2008-04-12 11:11 ` [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification of sctp_connectx() Ivan Skytte Jørgensen
2008-04-14  1:13 ` [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification Vlad Yasevich

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=47F3AB3D.7050906@hp.com \
    --to=vladislav.yasevich@hp.com \
    --cc=linux-sctp@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.