netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Morris <ipm@chirality.org.uk>
To: netdev@vger.kernel.org
Cc: Ian Morris <ipm@chirality.org.uk>
Subject: [PATCH net-next 0/2] ipv6: coding style - comparisons with NULL
Date: Sun, 29 Mar 2015 14:00:03 +0100	[thread overview]
Message-ID: <1427634005-4313-1-git-send-email-ipm@chirality.org.uk> (raw)

The following patches address some coding style issues only. No functional changes and no changes detected by objdiff.

The IPV6 code uses multiple different styles when comparing with NULL (I.e. x == NULL and !x as well as x != NULL and x). Generally the latter form is preferred according to checkpatch and so this changes aligns the code to this style. 

Ian Morris (2):
  ipv6: coding style: comparison for equality with NULL
  ipv6: coding style: comparison for inequality with NULL

 net/ipv6/addrconf.c        | 88 +++++++++++++++++++++++-----------------------
 net/ipv6/addrconf_core.c   |  2 +-
 net/ipv6/af_inet6.c        | 14 ++++----
 net/ipv6/ah6.c             |  2 +-
 net/ipv6/anycast.c         | 10 +++---
 net/ipv6/datagram.c        |  6 ++--
 net/ipv6/esp6.c            |  2 +-
 net/ipv6/exthdrs_core.c    | 10 +++---
 net/ipv6/icmp.c            | 13 ++++---
 net/ipv6/ip6_fib.c         |  4 +--
 net/ipv6/ip6_flowlabel.c   | 22 ++++++------
 net/ipv6/ip6_gre.c         | 14 ++++----
 net/ipv6/ip6_input.c       |  2 +-
 net/ipv6/ip6_offload.c     |  2 +-
 net/ipv6/ip6_output.c      | 24 ++++++-------
 net/ipv6/ip6_tunnel.c      | 12 +++----
 net/ipv6/ip6_vti.c         | 12 +++----
 net/ipv6/ip6mr.c           | 50 +++++++++++++-------------
 net/ipv6/ipv6_sockglue.c   | 10 +++---
 net/ipv6/mcast.c           | 30 ++++++++--------
 net/ipv6/ndisc.c           | 20 +++++------
 net/ipv6/raw.c             | 14 ++++----
 net/ipv6/reassembly.c      |  8 ++---
 net/ipv6/route.c           |  2 +-
 net/ipv6/sit.c             | 22 ++++++------
 net/ipv6/sysctl_net_ipv6.c |  2 +-
 net/ipv6/tcp_ipv6.c        | 20 +++++------
 net/ipv6/udp.c             | 14 ++++----
 net/ipv6/xfrm6_policy.c    |  2 +-
 29 files changed, 216 insertions(+), 217 deletions(-)

-- 
1.9.1

             reply	other threads:[~2015-03-29 13:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-29 13:00 Ian Morris [this message]
2015-03-29 13:00 ` [PATCH net-next 1/2] ipv6: coding style: comparison for equality with NULL Ian Morris
2015-03-29 13:00 ` [PATCH net-next 2/2] ipv6: coding style: comparison for inequality " Ian Morris
2015-03-29 17:36 ` [PATCH net-next 0/2] ipv6: coding style - comparisons " Joe Perches
2015-03-31 16:39   ` Ian Morris
2015-03-31 17:50     ` Joe Perches
2015-03-31 17:53 ` David Miller
     [not found]   ` <1427825806.10376.42.camel@perches.com>
2015-03-31 18:40     ` [PATCH] checkpatch/SubmittingPatches: Suggest line wrapping commit messages at 72 columns Joe Perches
2015-03-31 19:06       ` David Miller
2015-04-01 19:20       ` Andrew Morton
2015-04-01 19:28         ` Joe Perches
2015-04-01 19:36         ` Jonathan Corbet
2015-04-01 20:09           ` Joe Perches
2015-04-01 20:18             ` Andrew Morton
2015-04-01 20:33               ` [PATCH V2] checkpatch/SubmittingPatches: Suggest line wrapping commit messages at 75 columns Joe Perches

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=1427634005-4313-1-git-send-email-ipm@chirality.org.uk \
    --to=ipm@chirality.org.uk \
    --cc=netdev@vger.kernel.org \
    /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).