From: Ying Xue <ying.xue@windriver.com>
To: Willem de Bruijn <willemb@google.com>
Cc: David Miller <davem@davemloft.net>, <jon.maloy@ericsson.com>,
<Paul.Gortmaker@windriver.com>, <erik.hugne@ericsson.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Network Development <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: Wed, 11 Mar 2015 11:40:03 +0800 [thread overview]
Message-ID: <54FFB913.2060301@windriver.com> (raw)
In-Reply-To: <CA+FuTSdxmae0DnNnQdCgCdaThVtZ1raqEg9z6XpHE5N9u5MCfw@mail.gmail.com>
On 03/10/2015 11:41 PM, Willem de Bruijn wrote:
>> l
>> > 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 {
>> > if (!ipv6_addr_is_multicast(&remote->ipv6))
>> > return 0;
>> > err = __ipv6_sock_mc_join(sk, ub->ifindex, &remote->ipv6);
>> > +#endif
>> > }
>> > return err;
> It may also be prudent to initialize err to -EAFNOSUPPORT instead of
> 0. This function is currently only called when the protocol family has
> been checked, but relying on that is a bit fragile.
>
>
Thanks for your suggestion, and I will fix it in next version.
Regards,
Ying
next prev parent reply other threads:[~2015-03-11 3:40 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 [this message]
2015-03-10 18:50 ` Sergei Shtylyov
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=54FFB913.2060301@windriver.com \
--to=ying.xue@windriver.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=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.