netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yajun Deng <yajun.deng@linux.dev>
To: davem@davemloft.net, kuba@kernel.org, roopa@nvidia.com,
	nikolay@nvidia.com, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
	courmisch@gmail.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	bridge@lists.linux-foundation.org,
	linux-decnet-user@lists.sourceforge.net,
	linux-wireless@vger.kernel.org, Yajun Deng <yajun.deng@linux.dev>
Subject: [PATCH 0/4] Remove rtnetlink_send() in rtnetlink
Date: Mon, 19 Jul 2021 20:21:54 +0800	[thread overview]
Message-ID: <20210719122158.5037-1-yajun.deng@linux.dev> (raw)

rtnetlink_send() is similar to rtnl_notify(), there is no need for two 
functions to do the same thing. we can remove rtnetlink_send() and 
modify rtnl_notify() to adapt more case.

Patch1: remove rtnetlink_send() modify rtnl_notify() to adapt 
more case in rtnetlink.
Path2,Patch3: Adjustment parameters in rtnl_notify().
Path4: rtnetlink_send() already removed, use rtnl_notify() instead 
of rtnetlink_send().

Yajun Deng (4):
  rtnetlink: remove rtnetlink_send() in rtnetlink
  net: Adjustment parameters in rtnl_notify()
  vxlan: Adjustment parameters in rtnl_notify()
  net/sched: use rtnl_notify() instead of rtnetlink_send()

 drivers/net/vxlan.c       |  2 +-
 include/linux/rtnetlink.h |  7 +++----
 include/net/netlink.h     |  5 ++---
 net/bridge/br_fdb.c       |  2 +-
 net/bridge/br_mdb.c       |  4 ++--
 net/bridge/br_netlink.c   |  2 +-
 net/bridge/br_vlan.c      |  2 +-
 net/core/fib_rules.c      |  2 +-
 net/core/neighbour.c      |  2 +-
 net/core/net_namespace.c  |  2 +-
 net/core/rtnetlink.c      | 27 ++++++++-------------------
 net/dcb/dcbnl.c           |  2 +-
 net/decnet/dn_dev.c       |  2 +-
 net/decnet/dn_table.c     |  2 +-
 net/ipv4/devinet.c        |  4 ++--
 net/ipv4/fib_semantics.c  |  2 +-
 net/ipv4/fib_trie.c       |  2 +-
 net/ipv4/ipmr.c           |  4 ++--
 net/ipv4/nexthop.c        |  4 ++--
 net/ipv6/addrconf.c       |  8 ++++----
 net/ipv6/ip6mr.c          |  4 ++--
 net/ipv6/ndisc.c          |  2 +-
 net/ipv6/route.c          |  9 +++++----
 net/mpls/af_mpls.c        |  4 ++--
 net/phonet/pn_netlink.c   |  4 ++--
 net/sched/act_api.c       | 13 ++++++-------
 net/sched/cls_api.c       | 14 +++++++-------
 net/sched/sch_api.c       | 13 ++++++-------
 net/wireless/wext-core.c  |  2 +-
 29 files changed, 69 insertions(+), 83 deletions(-)

-- 
2.32.0


             reply	other threads:[~2021-07-19 12:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 12:21 Yajun Deng [this message]
2021-07-20 10:44 ` [PATCH 0/4] Remove rtnetlink_send() in rtnetlink Jakub Kicinski

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=20210719122158.5037-1-yajun.deng@linux.dev \
    --to=yajun.deng@linux.dev \
    --cc=bridge@lists.linux-foundation.org \
    --cc=courmisch@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-decnet-user@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=roopa@nvidia.com \
    --cc=xiyou.wangcong@gmail.com \
    --cc=yoshfuji@linux-ipv6.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).