netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	David Ahern <dsahern@kernel.org>
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
	Kuniyuki Iwashima <kuni1840@gmail.com>, <netdev@vger.kernel.org>
Subject: [PATCH v1 net-next 0/2] ipv6: Random cleanup for in6addr_any.
Date: Tue, 21 Mar 2023 18:22:02 -0700	[thread overview]
Message-ID: <20230322012204.33157-1-kuniyu@amazon.com> (raw)

The first patch removes in6addr_any alternatives and the second
removes redundant initialisation of a local variable.


Kuniyuki Iwashima (2):
  ipv6: Remove in6addr_any alternatives.
  6lowpan: Remove redundant initialisation of struct in6_addr.

 .../net/ethernet/mellanox/mlx5/core/en/tc_tun_encap.c |  5 ++---
 include/net/ip6_fib.h                                 |  9 +++------
 include/trace/events/fib.h                            |  5 ++---
 include/trace/events/fib6.h                           |  5 +----
 net/6lowpan/iphc.c                                    |  2 +-
 net/ethtool/ioctl.c                                   |  9 ++++-----
 net/ipv4/inet_hashtables.c                            | 11 ++++-------
 7 files changed, 17 insertions(+), 29 deletions(-)

-- 
2.30.2


             reply	other threads:[~2023-03-22  1:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  1:22 Kuniyuki Iwashima [this message]
2023-03-22  1:22 ` [PATCH v1 net-next 1/2] ipv6: Remove in6addr_any alternatives Kuniyuki Iwashima
2023-03-22  2:22   ` David Ahern
2023-03-22  2:42     ` Kuniyuki Iwashima
2023-03-22  1:22 ` [PATCH v1 net-next 2/2] 6lowpan: Remove redundant initialisation of struct in6_addr Kuniyuki Iwashima

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=20230322012204.33157-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).