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 v2 net-next 0/2] ipv6: Random cleanup for in6addr_any.
Date: Mon, 27 Mar 2023 16:54:53 -0700 [thread overview]
Message-ID: <20230327235455.52990-1-kuniyu@amazon.com> (raw)
The first patch removes in6addr_any alternatives and the second
removes redundant initialisation of a local variable.
Changes:
v2: Use ipv6_addr_any() in patch 1. (David Ahern)
v1: https://lore.kernel.org/netdev/20230322012204.33157-1-kuniyu@amazon.com/
Kuniyuki Iwashima (2):
ipv6: Remove in6addr_any alternatives.
6lowpan: Remove redundant initialisation.
.../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 | 10 +++++-----
net/ipv4/inet_hashtables.c | 11 ++++-------
7 files changed, 18 insertions(+), 29 deletions(-)
--
2.30.2
next reply other threads:[~2023-03-27 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 23:54 Kuniyuki Iwashima [this message]
2023-03-27 23:54 ` [PATCH v2 net-next 1/2] ipv6: Remove in6addr_any alternatives Kuniyuki Iwashima
2023-03-28 6:27 ` Mark Bloch
2023-03-28 14:32 ` David Ahern
2023-03-27 23:54 ` [PATCH v2 net-next 2/2] 6lowpan: Remove redundant initialisation Kuniyuki Iwashima
2023-03-28 6:27 ` Mark Bloch
2023-03-28 19:00 ` Kuniyuki Iwashima
2023-03-29 8:00 ` [PATCH v2 net-next 0/2] ipv6: Random cleanup for in6addr_any patchwork-bot+netdevbpf
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=20230327235455.52990-1-kuniyu@amazon.com \
--to=kuniyu@amazon$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kuni1840@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(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