netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 00/11] sctp: remove typedefs from structures part 3
Date: Sun, 23 Jul 2017 09:34:25 +0800	[thread overview]
Message-ID: <cover.1500773578.git.lucien.xin@gmail.com> (raw)

As we know, typedef is suggested not to use in kernel, even checkpatch.pl
also gives warnings about it. Now sctp is using it for many structures.

All this kind of typedef's using should be removed. This patchset is the
part 3 to remove it for another 11 basic structures from linux/sctp.h.

Just as the part 1 and 2, No any code's logic would be changed in these
patches, only cleaning up.

Xin Long (11):
  sctp: remove the typedef sctp_initack_chunk_t
  sctp: remove the typedef sctp_cookie_param_t
  sctp: remove the typedef sctp_unrecognized_param_t
  sctp: remove the typedef sctp_gap_ack_block_t
  sctp: remove the typedef sctp_dup_tsn_t
  sctp: remove the typedef sctp_sack_variable_t
  sctp: remove the typedef sctp_sackhdr_t
  sctp: remove the typedef sctp_sack_chunk_t
  sctp: remove the typedef sctp_heartbeathdr_t
  sctp: remove the typedef sctp_heartbeat_chunk_t
  sctp: remove the typedef sctp_abort_chunk_t

 include/linux/sctp.h       | 53 +++++++++++++++++++++++-----------------------
 include/net/sctp/command.h |  4 ++--
 net/sctp/chunk.c           |  2 +-
 net/sctp/outqueue.c        | 10 ++++-----
 net/sctp/sm_make_chunk.c   | 18 +++++++++-------
 net/sctp/sm_statefuns.c    | 50 ++++++++++++++++++++-----------------------
 6 files changed, 68 insertions(+), 69 deletions(-)

-- 
2.1.0

             reply	other threads:[~2017-07-23  1:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-23  1:34 Xin Long [this message]
2017-07-23  1:34 ` [PATCH net-next 01/11] sctp: remove the typedef sctp_initack_chunk_t Xin Long
2017-07-23  1:34   ` [PATCH net-next 02/11] sctp: remove the typedef sctp_cookie_param_t Xin Long
2017-07-23  1:34     ` [PATCH net-next 03/11] sctp: remove the typedef sctp_unrecognized_param_t Xin Long
2017-07-23  1:34       ` [PATCH net-next 04/11] sctp: remove the typedef sctp_gap_ack_block_t Xin Long
2017-07-23  1:34         ` [PATCH net-next 05/11] sctp: remove the typedef sctp_dup_tsn_t Xin Long
2017-07-23  1:34           ` [PATCH net-next 06/11] sctp: remove the typedef sctp_sack_variable_t Xin Long
2017-07-23  1:34             ` [PATCH net-next 07/11] sctp: remove the typedef sctp_sackhdr_t Xin Long
2017-07-23  1:34               ` [PATCH net-next 08/11] sctp: remove the typedef sctp_sack_chunk_t Xin Long
2017-07-23  1:34                 ` [PATCH net-next 09/11] sctp: remove the typedef sctp_heartbeathdr_t Xin Long
2017-07-23  1:34                   ` [PATCH net-next 10/11] sctp: remove the typedef sctp_heartbeat_chunk_t Xin Long
2017-07-23  1:34                     ` [PATCH net-next 11/11] sctp: remove the typedef sctp_abort_chunk_t Xin Long
2017-07-24 23:01 ` [PATCH net-next 00/11] sctp: remove typedefs from structures part 3 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.1500773578.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).