From: Wangyufen <wangyufen@huawei.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <ioe@perches.com>, <kuznet@ms2.inr.ac.ru>,
Wang Yufen <wangyufen@huawei.com>
Subject: [PATCH net-next v4 0/3] ipv6: tcp_ipv6 policy route issue
Date: Fri, 28 Mar 2014 12:01:40 +0800 [thread overview]
Message-ID: <1395979303-7668-1-git-send-email-wangyufen@huawei.com> (raw)
From: Wang Yufen <wangyufen@huawei.com>
Wang Yufen (3):
ipv6: tcp_ipv6 do some cleanup
ipv6: reuse rt6_need_strict
ipv6: tcp_ipv6 policy route issue
v4: use rt6_need_strict to check whether the oif directly
assigned to iif
include/net/ip6_route.h | 1 +
net/ipv6/route.c | 2 +-
net/ipv6/ip6_fib.c | 42 +++---
3 file changed, 24 insertions(+), 21 deletions(-)
--
1.7.12
next reply other threads:[~2014-03-28 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 4:01 Wangyufen [this message]
2014-03-28 4:01 ` [PATCH net-next v4 1/3] ipv6: tcp_ipv6 do some cleanup Wangyufen
2014-03-28 4:01 ` [PATCH net-next v4 2/3] ipv6: reuse rt6_need_strict Wangyufen
2014-03-28 7:41 ` Hannes Frederic Sowa
2014-03-28 9:04 ` wangyufen
2014-03-28 4:01 ` [PATCH net-next v4 3/3] ipv6: tcp_ipv6 policy route issue Wangyufen
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=1395979303-7668-1-git-send-email-wangyufen@huawei.com \
--to=wangyufen@huawei.com \
--cc=davem@davemloft.net \
--cc=ioe@perches.com \
--cc=kuznet@ms2.inr.ac.ru \
--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).