From: Wei Yongjun <yjwei@cn•fujitsu.com>
To: David Miller <davem@davemloft•net>
Cc: "netdev@vger•kernel.org" <netdev@vger•kernel.org>,
lksctp <linux-sctp@vger•kernel.org>
Subject: [PATCH net-next-2.6 0/5 v2] SCTP updates for net-next-2.6
Date: Wed, 27 Apr 2011 15:35:25 +0800 [thread overview]
Message-ID: <4DB7C73D.3000406@cn.fujitsu.com> (raw)
Hi David
Here is a set of SCTP patches for net-next-2.6, the last part
from vlad's lksctp-dev tree, update SCTP IPv6 routing and IPSec
issues. Please apply.
Changelog:
- redo the intermediate builds test and function test.
- remove useless ->dst_saddr member of sctp_pf
- merge some fix for original patch
Vlad Yasevich (4):
sctp: cache the ipv6 source after route lookup
sctp: make sctp over IPv6 work with IPsec
sctp: remove useless arguments from get_saddr() call
sctp: clean up route lookup calls
Weixing Shi (1):
sctp: fix sctp to work with ipv6 source address routing
include/net/sctp/structs.h | 18 ++---
net/sctp/ipv6.c | 183 +++++++++++++++++++++++++------------------
net/sctp/protocol.c | 54 ++++++-------
net/sctp/socket.c | 2 +-
net/sctp/transport.c | 28 ++++---
5 files changed, 153 insertions(+), 132 deletions(-)
next reply other threads:[~2011-04-27 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 7:35 Wei Yongjun [this message]
2011-04-27 7:36 ` [PATCH net-next-2.6 1/5 v2] sctp: fix sctp to work with ipv6 source address routing Wei Yongjun
2011-04-27 7:51 ` [PATCH net-next-2.6 2/5 v2] sctp: cache the ipv6 source after route lookup Wei Yongjun
2011-04-27 7:52 ` [PATCH net-next-2.6 3/5] sctp: make sctp over IPv6 work with IPsec Wei Yongjun
2011-04-27 7:53 ` [PATCH net-next-2.6 4/5 v2] sctp: remove useless arguments from get_saddr() call Wei Yongjun
2011-04-27 7:54 ` [PATCH net-next-2.6 5/5 v2] sctp: clean up route lookup calls Wei Yongjun
2011-04-27 20:20 ` [PATCH net-next-2.6 0/5 v2] SCTP updates for net-next-2.6 David 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=4DB7C73D.3000406@cn.fujitsu.com \
--to=yjwei@cn$(echo .)fujitsu.com \
--cc=davem@davemloft$(echo .)net \
--cc=linux-sctp@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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