From: David Miller <davem@davemloft.net>
To: brian.haley@hp.com
Cc: greearb@candelatech.com, netdev@vger.kernel.org
Subject: Re: [net-next] ipv6: Enable netlink notification for tentative addresses.
Date: Thu, 26 Aug 2010 13:18:01 -0700 (PDT) [thread overview]
Message-ID: <20100826.131801.246519955.davem@davemloft.net> (raw)
In-Reply-To: <4C76C73F.4080206@hp.com>
From: Brian Haley <brian.haley@hp.com>
Date: Thu, 26 Aug 2010 15:57:51 -0400
> But then we get a message for an address that can't be used because
> it hasn't passed DAD, I'm not so sure that is a good thing,
> especially if we don't get notified when it passes DAD.
I think that we shouldn't send notifications for an address that can't
even be used. So essentially I argue against this patch in any form :)
next prev parent reply other threads:[~2010-08-26 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 18:26 [net-next] ipv6: Enable netlink notification for tentative addresses Ben Greear
2010-08-26 4:24 ` David Miller
2010-08-26 18:50 ` Ben Greear
2010-08-26 19:57 ` Brian Haley
2010-08-26 20:18 ` David Miller [this message]
2010-08-26 21:19 ` Ben Greear
2010-08-26 21:27 ` David Miller
2010-08-27 4:24 ` Ben Greear
2010-08-26 21:22 ` Ben Greear
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=20100826.131801.246519955.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brian.haley@hp.com \
--cc=greearb@candelatech.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).