public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail•com>
To: netdev@vger•kernel.org
Cc: linux-sctp@vger•kernel.org, Neil Horman <nhorman@tuxdriver•com>,
	Vlad Yasevich <vyasevich@gmail•com>,
	David Miller <davem@davemloft•net>,
	David Laight <David.Laight@ACULAB•COM>
Subject: [PATCH next v3 0/2] Rename WORD_TRUNC/ROUND macros and use them
Date: Wed, 21 Sep 2016 08:45:54 -0300	[thread overview]
Message-ID: <cover.1474457954.git.marcelo.leitner@gmail.com> (raw)

This patchset aims to rename these macros to a non-confusing name, as
reported by David Laight and David Miller, and to update all remaining
places to make use of it, which was 1 last remaining spot.

v3:
- Name it SCTP_PAD4 instead of SCTP_ALIGN4, as suggested by David Laight
v2:
- fixed 2nd patch summary

Details on the specific changelogs.

Thanks!

Marcelo Ricardo Leitner (2):
  sctp: rename WORD_TRUNC/ROUND macros
  sctp: make use of WORD_TRUNC macro

 include/net/sctp/sctp.h  | 10 +++++-----
 net/netfilter/xt_sctp.c  |  2 +-
 net/sctp/associola.c     |  2 +-
 net/sctp/chunk.c         | 13 +++++++------
 net/sctp/input.c         |  8 ++++----
 net/sctp/inqueue.c       |  2 +-
 net/sctp/output.c        | 12 ++++++------
 net/sctp/sm_make_chunk.c | 28 ++++++++++++++--------------
 net/sctp/sm_statefuns.c  |  6 +++---
 net/sctp/transport.c     |  4 ++--
 net/sctp/ulpevent.c      |  4 ++--
 11 files changed, 46 insertions(+), 45 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-09-21 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 11:45 Marcelo Ricardo Leitner [this message]
2016-09-21 11:45 ` [PATCH next v3 1/2] sctp: rename WORD_TRUNC/ROUND macros Marcelo Ricardo Leitner
2016-09-21 11:45 ` [PATCH next v3 2/2] sctp: make use of SCTP_TRUNC4 macro Marcelo Ricardo Leitner
2016-09-21 15:37 ` [PATCH next v3 0/2] Rename WORD_TRUNC/ROUND macros and use them Neil Horman
2016-09-22  7:13 ` 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.1474457954.git.marcelo.leitner@gmail.com \
    --to=marcelo.leitner@gmail$(echo .)com \
    --cc=David.Laight@ACULAB$(echo .)COM \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-sctp@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=nhorman@tuxdriver$(echo .)com \
    --cc=vyasevich@gmail$(echo .)com \
    /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