From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: duanj.fnst@cn.fujitsu.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: drop the judgement in rt6_alloc_cow()
Date: Tue, 05 Nov 2013 22:17:34 -0500 (EST) [thread overview]
Message-ID: <20131105.221734.996824909093482711.davem@davemloft.net> (raw)
In-Reply-To: <20131105212344.GM8832@order.stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Tue, 5 Nov 2013 22:23:44 +0100
> On Tue, Nov 05, 2013 at 01:34:53PM +0800, Duan Jiong wrote:
>>
>> Now rt6_alloc_cow() is only called by ip6_pol_route() when
>> rt->rt6i_flags doesn't contain both RTF_NONEXTHOP and RTF_GATEWAY,
>> and rt->rt6i_flags hasn't been changed in ip6_rt_copy().
>> So there is no neccessary to judge whether rt->rt6i_flags contains
>> RTF_GATEWAY or not.
>
> This is ok.
>
> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Applied, thanks everyone.
prev parent reply other threads:[~2013-11-06 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 5:34 [PATCH] ipv6: drop the judgement in rt6_alloc_cow() Duan Jiong
2013-11-05 21:23 ` Hannes Frederic Sowa
2013-11-06 3:17 ` 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=20131105.221734.996824909093482711.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=duanj.fnst@cn.fujitsu.com \
--cc=hannes@stressinduktion.org \
--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).