From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Ying Xue <ying.xue@windriver.com>, davem@davemloft.net
Cc: jon.maloy@ericsson.com, Paul.Gortmaker@windriver.com,
erik.hugne@ericsson.com, fengguang.wu@intel.com,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
kbuild-all@01.org
Subject: Re: [PATCH net-next v2] tipc: fix undefined __ipv6_sock_mc_join compile error
Date: Tue, 10 Mar 2015 21:50:09 +0300 [thread overview]
Message-ID: <54FF3CE1.3080804@cogentembedded.com> (raw)
In-Reply-To: <1425976885-18258-1-git-send-email-ying.xue@windriver.com>
Hello.
On 03/10/2015 11:41 AM, Ying Xue wrote:
> When CONFIG_IPV6 option is disabled, below error will appear while
> building TIPC module:
> ERROR: "__ipv6_sock_mc_join" [net/tipc/tipc.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [net/tipc/tipc.ko] Error 1
> This is because we don't check whether or not the CONFIG_IPV6 is
> enabled when calling __ipv6_sock_mc_join().
> In addition, especially when TIPC=y, TIPC_MEDIA_UDP=y, and IPV6=m, TIPC
> module is also unable to be successfully built. Therefore, we add a
> dependency condition like (IPV6 || IPV6=n) to avoid the error.
> Fixes: d0f91938bede ("tipc: add ip/udp media type")
> Reported-by: Wu Fengguang <fengguang.wu@intel.com>
> Cc: Kbuild test robot <kbuild-all@01.org>
> Signed-off-by: Ying Xue <ying.xue@windriver.com>
> ---
> v2:
> Fix another compile error when TIPC=y, TIPC_MEDIA_UDP=y, and IPV6=m
> net/tipc/Kconfig | 1 +
> net/tipc/udp_media.c | 2 ++
> 2 files changed, 3 insertions(+)
> diff --git a/net/tipc/Kconfig b/net/tipc/Kconfig
> index c25a3a1..6f217ba 100644
> --- a/net/tipc/Kconfig
> +++ b/net/tipc/Kconfig
> @@ -5,6 +5,7 @@
> menuconfig TIPC
> tristate "The TIPC Protocol"
> depends on INET
> + depends on (IPV6 || IPV6=n)
Parens not needed.
[...]
> diff --git a/net/tipc/udp_media.c b/net/tipc/udp_media.c
> index fc2fb11..6763002 100644
> --- a/net/tipc/udp_media.c
> +++ b/net/tipc/udp_media.c
> @@ -247,10 +247,12 @@ static int enable_mcast(struct udp_bearer *ub, struct udp_media_addr *remote)
> mreqn.imr_multiaddr = remote->ipv4;
> mreqn.imr_ifindex = ub->ifindex;
> err = __ip_mc_join_group(sk, &mreqn);
> +#if IS_ENABLED(CONFIG_IPV6)
> } else {
How about:
} else if (IS_ENABLED(CONFIG_IPV6)) {
> if (!ipv6_addr_is_multicast(&remote->ipv6))
> return 0;
> err = __ipv6_sock_mc_join(sk, ub->ifindex, &remote->ipv6);
> +#endif
> }
> return err;
> }
WBR, Sergei
next prev parent reply other threads:[~2015-03-10 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 8:41 [PATCH net-next v2] tipc: fix undefined __ipv6_sock_mc_join compile error Ying Xue
2015-03-10 15:41 ` Willem de Bruijn
2015-03-10 16:47 ` David Miller
2015-03-11 3:11 ` Ying Xue
2015-03-11 4:05 ` David Miller
2015-03-11 6:24 ` Ying Xue
2015-03-11 3:40 ` Ying Xue
2015-03-10 18:50 ` Sergei Shtylyov [this message]
2015-03-11 3:34 ` Ying Xue
2015-03-11 14:34 ` Sergei Shtylyov
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=54FF3CE1.3080804@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=Paul.Gortmaker@windriver.com \
--cc=davem@davemloft.net \
--cc=erik.hugne@ericsson.com \
--cc=fengguang.wu@intel.com \
--cc=jon.maloy@ericsson.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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).