From: Cong Wang <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: [RFC net-next] ipv6 route: Do not attach neighbour on route.
Date: Tue, 15 Jan 2013 02:37:24 +0000 (UTC) [thread overview]
Message-ID: <kd2fd3$5cv$1@ger.gmane.org> (raw)
In-Reply-To: 50F463E5.7070206@linux-ipv6.org
On Mon, 14 Jan 2013 at 20:00 GMT, YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org> wrote:
> Not tested, just an RFC.
> Depends on previous new_neigh removal from netevent patch (sorry).
>
Forgot to define __ipv6_neigh_lookup_noref()?
prev parent reply other threads:[~2013-01-15 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 20:00 [RFC net-next] ipv6 route: Do not attach neighbour on route YOSHIFUJI Hideaki
2013-01-15 2:37 ` Cong Wang [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='kd2fd3$5cv$1@ger.gmane.org' \
--to=xiyou.wangcong@gmail.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).