From: Sun Shouxin <sunshouxin@chinatelecom.cn>
To: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, oliver@neukum.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
huyd12@chinatelecom.cn, sunshouxin@chinatelecom.cn
Subject: [PATCH v6 3/4] net:ipv6:Export inet6_ifa_finish_destroy and ipv6_get_ifaddr
Date: Wed, 23 Mar 2022 08:09:05 -0400 [thread overview]
Message-ID: <20220323120906.42692-4-sunshouxin@chinatelecom.cn> (raw)
In-Reply-To: <20220323120906.42692-1-sunshouxin@chinatelecom.cn>
Export inet6_ifa_finish_destroy and ipv6_get_ifaddr for bonding usage.
Signed-off-by: Sun Shouxin <sunshouxin@chinatelecom.cn>
---
net/ipv6/addrconf.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index bb1912eacd90..6825d70c34fb 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -975,6 +975,7 @@ void inet6_ifa_finish_destroy(struct inet6_ifaddr *ifp)
kfree_rcu(ifp, rcu);
}
+EXPORT_SYMBOL(inet6_ifa_finish_destroy);
static void
ipv6_link_dev_addr(struct inet6_dev *idev, struct inet6_ifaddr *ifp)
@@ -2037,6 +2038,7 @@ struct inet6_ifaddr *ipv6_get_ifaddr(struct net *net, const struct in6_addr *add
return result;
}
+EXPORT_SYMBOL(ipv6_get_ifaddr);
/* Gets referenced address, destroys ifaddr */
--
2.27.0
next prev parent reply other threads:[~2022-03-23 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 12:09 [PATCH v6 0/4] Add support for IPV6 RLB to balance-alb mode Sun Shouxin
2022-03-23 12:09 ` [PATCH v6 1/4] net:ipv6:Add void *data to ndisc_send_na function Sun Shouxin
2022-03-23 12:09 ` [PATCH v6 2/4] net:ipv6:Refactor ndisc_send_na to support sending na by slave directly Sun Shouxin
2022-03-23 12:09 ` Sun Shouxin [this message]
2022-03-23 12:09 ` [PATCH v6 4/4] net:bonding:Add support for IPV6 RLB to balance-alb mode Sun Shouxin
2022-03-23 14:35 ` [PATCH v6 0/4] Add " David Ahern
2022-03-23 15:33 ` Jakub Kicinski
2022-03-23 16:38 ` Jay Vosburgh
2022-03-23 17:28 ` Jakub Kicinski
2022-03-24 2:00 ` 孙守鑫
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=20220323120906.42692-4-sunshouxin@chinatelecom.cn \
--to=sunshouxin@chinatelecom.cn \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=huyd12@chinatelecom.cn \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=pabeni@redhat.com \
--cc=vfalico@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