From: "David S. Miller" <davem@redhat.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: dwmw2@infradead.org, netdev@oss.sgi.com,
marcelo.tosatti@cyclades.com,
lksctp-developers@lists.sourceforge.net
Subject: Re: SCTP sockopt discrepancy between 2.4 and 2.6.
Date: Mon, 2 Feb 2004 11:21:50 -0800 [thread overview]
Message-ID: <20040202112150.3c8d5218.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402021056290.2352@localhost.localdomain>
I appreciate your status report Sridhar, thank you.
But the fact of the matter is that 2.4.x and 2.6.x cannot export two
totally incompatible user visible APIs for the SCTP socket layer.
This is something which must be fixed, not something we would like to
be fixed :-)
next prev parent reply other threads:[~2004-02-02 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 18:43 SCTP sockopt discrepancy between 2.4 and 2.6 David Woodhouse
2004-02-02 19:03 ` David S. Miller
2004-02-02 19:09 ` Sridhar Samudrala
2004-02-02 19:21 ` David S. Miller [this message]
2004-02-03 18:13 ` Sridhar Samudrala
2004-02-03 18:19 ` David S. Miller
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=20040202112150.3c8d5218.davem@redhat.com \
--to=davem@redhat.com \
--cc=dwmw2@infradead.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.com \
--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).