From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: davem@davemloft.net,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
Vlad Yasevich <vyasevich@gmail.com>
Subject: [PATCH net 0/3] sctp: fix some other sparse errors
Date: Sun, 26 Nov 2017 20:16:05 +0800 [thread overview]
Message-ID: <cover.1511698478.git.lucien.xin@gmail.com> (raw)
After the last fixes for sparse errors, there are still three sparse
errors in sctp codes, two of them are type cast, and the other one
is using extern.
Xin Long (3):
sctp: force SCTP_ERROR_INV_STRM with __u32 when calling
sctp_chunk_fail
sctp: force the params with right types for sctp csum apis
sctp: remove extern from stream sched
include/net/sctp/checksum.h | 13 +++++++------
include/net/sctp/sctp.h | 5 +++++
include/net/sctp/stream_sched.h | 5 +++++
net/sctp/protocol.c | 1 +
net/sctp/stream.c | 2 +-
net/sctp/stream_sched.c | 25 ++++++++++++++++++-------
net/sctp/stream_sched_prio.c | 7 ++++++-
net/sctp/stream_sched_rr.c | 7 ++++++-
8 files changed, 49 insertions(+), 16 deletions(-)
--
2.1.0
next reply other threads:[~2017-11-26 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 12:16 Xin Long [this message]
2017-11-26 12:16 ` [PATCH net 1/3] sctp: force SCTP_ERROR_INV_STRM with __u32 when calling sctp_chunk_fail Xin Long
2017-11-26 12:16 ` [PATCH net 2/3] sctp: force the params with right types for sctp csum apis Xin Long
2017-11-26 12:16 ` [PATCH net 3/3] sctp: remove extern from stream sched Xin Long
2017-11-27 12:41 ` Marcelo Ricardo Leitner
2017-11-27 12:32 ` [PATCH net 2/3] sctp: force the params with right types for sctp csum apis Marcelo Ricardo Leitner
2017-11-27 12:32 ` [PATCH net 1/3] sctp: force SCTP_ERROR_INV_STRM with __u32 when calling sctp_chunk_fail Marcelo Ricardo Leitner
2017-11-27 14:00 ` [PATCH net 0/3] sctp: fix some other sparse errors Neil Horman
2017-11-28 16:00 ` 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=cover.1511698478.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 \
--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).