From: David Miller <davem@davemloft.net>
To: lw@cn.fujitsu.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: Set mcast_hops to IPV6_DEFAULT_MCASTHOPS when -1 was given.
Date: Mon, 28 Nov 2011 18:09:35 -0500 (EST) [thread overview]
Message-ID: <20111128.180935.774474803377807469.davem@davemloft.net> (raw)
In-Reply-To: <4ED3394E.7050602@cn.fujitsu.com>
From: Li Wei <lw@cn.fujitsu.com>
Date: Mon, 28 Nov 2011 15:33:34 +0800
> We need to set np->mcast_hops to it's default value at this moment
> otherwise when we use it and found it's value is -1, the logic to
> get default hop limit doesn't take multicast into account and will
> return wrong hop limit(IPV6_DEFAULT_HOPLIMIT) which is for unicast.
>
> Signed-off-by: Li Wei <lw@cn.fujitsu.com>
Applied, thank you.
prev parent reply other threads:[~2011-11-28 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 7:33 [PATCH] ipv6: Set mcast_hops to IPV6_DEFAULT_MCASTHOPS when -1 was given Li Wei
2011-11-28 23:09 ` David Miller [this message]
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=20111128.180935.774474803377807469.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lw@cn.fujitsu.com \
--cc=netdev@vger.kernel.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).