From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
davem@davemloft.net
Subject: [PATCH net-next 0/4] sctp: add some missing events from rfc5061
Date: Tue, 8 Oct 2019 19:27:32 +0800 [thread overview]
Message-ID: <cover.1570534014.git.lucien.xin@gmail.com> (raw)
There are 4 events defined in rfc5061 missed in linux sctp:
SCTP_ADDR_ADDED, SCTP_ADDR_REMOVED, SCTP_ADDR_MADE_PRIM and
SCTP_SEND_FAILED_EVENT.
This patchset is to add them up.
Xin Long (4):
sctp: add SCTP_ADDR_ADDED event
sctp: add SCTP_ADDR_REMOVED event
sctp: add SCTP_ADDR_MADE_PRIM event
sctp: add SCTP_SEND_FAILED_EVENT event
include/net/sctp/ulpevent.h | 16 +++++++------
include/uapi/linux/sctp.h | 16 ++++++++++++-
net/sctp/associola.c | 22 +++++++----------
net/sctp/chunk.c | 40 +++++++++++++++----------------
net/sctp/ulpevent.c | 57 ++++++++++++++++++++++++++++++++++++++++++++-
5 files changed, 108 insertions(+), 43 deletions(-)
--
2.1.0
next reply other threads:[~2019-10-08 11:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 11:27 Xin Long [this message]
2019-10-08 11:27 ` [PATCH net-next 1/4] sctp: add SCTP_ADDR_ADDED event Xin Long
2019-10-08 11:27 ` [PATCH net-next 2/4] sctp: add SCTP_ADDR_REMOVED event Xin Long
2019-10-08 11:27 ` [PATCH net-next 3/4] sctp: add SCTP_ADDR_MADE_PRIM event Xin Long
2019-10-08 11:27 ` [PATCH net-next 4/4] sctp: add SCTP_SEND_FAILED_EVENT event Xin Long
2019-10-09 18:13 ` [PATCH net-next 0/4] sctp: add some missing events from rfc5061 Neil Horman
2019-10-10 0:13 ` Jakub Kicinski
2020-04-19 10:25 ` ABI breakage in sctp_event_subscribe (was [PATCH net-next 0/4] sctp: add some missing events from rfc5061) Harald Welte
2020-05-01 13:16 ` Harald Welte
2020-05-01 14:20 ` Marcelo Ricardo Leitner
2020-06-01 10:46 ` Harald Welte
2020-06-01 12:14 ` Neil Horman
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=cover.1570534014.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).