From: David Miller <davem@davemloft.net>
To: lucien.xin@gmail.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
marcelo.leitner@gmail.com, nhorman@tuxdriver.com,
vyasevich@gmail.com
Subject: Re: [PATCHv2 net-next 0/7] sctp: add receiver-side procedures for stream reconf asoc reset and add streams and response
Date: Sun, 12 Mar 2017 23:22:45 -0700 (PDT) [thread overview]
Message-ID: <20170312.232245.410360677237076869.davem@davemloft.net> (raw)
In-Reply-To: <cover.1489118815.git.lucien.xin@gmail.com>
From: Xin Long <lucien.xin@gmail.com>
Date: Fri, 10 Mar 2017 12:11:05 +0800
> Patch 2/7, 4/7, 5/7, 6/7 are to implement the process of asoc reset request,
> add streams requests and all kinds of responses.
>
> Patch 1/7 and 3/7 are ahead of 2/7 and 4/7 to add two event notification
> for asoc reset and add streams.
>
> Patch 7/7 is the last patch for implementing rfc6525 sctp stream reconf
> to add sysctl and sockopt interface for users to enable sctp stream reconf.
>
> After this patchset, sctp stream reconf will be able to work as rfc6525.
>
> v1->v2:
> - put these into a smaller group.
> - rename the titles of the commits and improve some changelogs.
> - improve sctp_chunk_lookup_strreset_param and reuse it in patch 4/7.
> - process addstrm outreq as the ack of in addstrm inreq if strreset_chunk
> is not NULL in patch 4/7.
> - remove the stream alloc when sending addstrm inreq, and the process in
> peer will response it by sending a addstrm out request back in patch 5/7.
> - adjust the process of addstrm in resp to fit in the codes that only alloc
> streams through addstrm outreq in patch 6/7.
Series applied, thanks.
prev parent reply other threads:[~2017-03-13 6:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 4:11 [PATCHv2 net-next 0/7] sctp: add receiver-side procedures for stream reconf asoc reset and add streams and response Xin Long
2017-03-10 4:11 ` [PATCHv2 net-next 1/7] sctp: add support for generating assoc reset event notification Xin Long
2017-03-10 4:11 ` [PATCHv2 net-next 2/7] sctp: implement receiver-side procedures for the SSN/TSN Reset Request Parameter Xin Long
2017-03-10 4:11 ` [PATCHv2 net-next 3/7] sctp: add support for generating add stream change event notification Xin Long
2017-03-10 4:11 ` [PATCHv2 net-next 4/7] sctp: implement receiver-side procedures for the Add Outgoing Streams Request Parameter Xin Long
2017-03-10 4:11 ` [PATCHv2 net-next 5/7] sctp: implement receiver-side procedures for the Add Incoming " Xin Long
2017-03-10 4:11 ` [PATCHv2 net-next 6/7] sctp: implement receiver-side procedures for the Reconf Response Parameter Xin Long
2017-03-10 4:11 ` [PATCHv2 net-next 7/7] sctp: add get and set sockopt for reconf_enable Xin Long
2017-03-20 18:04 ` [PATCHv2 net-next 2/7] sctp: implement receiver-side procedures for the SSN/TSN Reset Request Parameter Marcelo Ricardo Leitner
2017-03-21 5:44 ` Xin Long
2017-03-24 23:52 ` Marcelo Ricardo Leitner
2017-03-27 4:48 ` Xin Long
2017-03-27 14:16 ` Marcelo Ricardo Leitner
2017-03-27 15:50 ` Xin Long
2017-03-10 4:17 ` [PATCHv2 net-next 0/7] sctp: add receiver-side procedures for stream reconf asoc reset and add streams and response Xin Long
2017-03-13 6:22 ` David Miller [this message]
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=20170312.232245.410360677237076869.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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).