From: David Miller <davem@davemloft.net>
To: mleitner@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: do not create neighbor entries for local delivery
Date: Wed, 16 Jan 2013 16:28:13 -0500 (EST) [thread overview]
Message-ID: <20130116.162813.1734293658687337225.davem@davemloft.net> (raw)
In-Reply-To: <50F6ABCA.4020804@redhat.com>
From: Marcelo Ricardo Leitner <mleitner@redhat.com>
Date: Wed, 16 Jan 2013 11:31:54 -0200
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index
> 7c34c01b515b7ac370f8021ba6f5ec4c654e9e41..b63e33bcbdfbc1bd78af0b98ffc2d211805214ea
> 100644
Patch corrupted by your email client.
Note also that YOSHIFUJI Hideaki's patches to remove the cached neighbour
entirely from ipv6 routes will have the same effect, so your patch won't
be needed.
next prev parent reply other threads:[~2013-01-16 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 13:31 [PATCH] ipv6: do not create neighbor entries for local delivery Marcelo Ricardo Leitner
2013-01-16 21:28 ` David Miller [this message]
2013-01-17 11:17 ` Marcelo Ricardo Leitner
2013-01-29 10:53 ` Jiri Pirko
2013-01-29 21:10 ` David Miller
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=20130116.162813.1734293658687337225.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mleitner@redhat.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).