netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	tgraf@suug.ch, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH 09/16] [IPv6] address: Convert address notification to use rtnl_notify()
Date: Mon, 14 Aug 2006 23:03:34 -0400	[thread overview]
Message-ID: <1155611014.6946.82.camel@jzny2> (raw)
In-Reply-To: <1155609965.6946.74.camel@jzny2>

On Mon, 2006-14-08 at 22:46 -0400, jamal wrote:
> On Tue, 2006-15-08 at 10:56 +1000, Herbert Xu wrote:
> Thats all the quagga
> and other folks were looking for in cases where it was ambigous. 
> 

Just to be clear, when Alexey says "that past discussion essentially
closed the question." he is correct and i did not, hopefully, insuniate
otherwise. The question i posed above is still valid though ;->

cheers,
jamal




  reply	other threads:[~2006-08-15  3:03 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 21:37 [PATCHSET] rtnetlink notification rework Thomas Graf
2006-08-13 22:00 ` [PATCH 01/16] [RTNETLINK]: Use rtnl_unicast() for rtnetlink unicasts Thomas Graf
2006-08-13 22:00 ` [PATCH 02/16] [NETLINK]: Add notification message sending interface Thomas Graf
2006-08-13 22:00 ` [PATCH 03/16] [RTNETLINK]: Add rtnetlink notification interface Thomas Graf
2006-08-13 22:00 ` [PATCH 04/16] [NET] fib_rules: Convert fib rule notification to use rtnl_notify() Thomas Graf
2006-08-13 22:00 ` [PATCH 05/16] [NEIGH]: Convert neighbour notifications ot " Thomas Graf
2006-08-13 22:00 ` [PATCH 06/16] [DECNET]: Convert DECnet notifications to " Thomas Graf
2006-08-13 22:00 ` [PATCH 07/16] [IPv4] address: Convert address notification " Thomas Graf
2006-08-13 22:00 ` [PATCH 08/16] [IPv4] route: Convert route notifications " Thomas Graf
2006-08-13 22:00 ` [PATCH 09/16] [IPv6] address: Convert address notification " Thomas Graf
2006-08-14 23:43   ` jamal
2006-08-14 23:51     ` jamal
2006-08-15  7:20       ` Hasso Tepper
2006-08-15  9:50         ` jamal
2006-08-15  0:07     ` Thomas Graf
2006-08-15  0:12       ` jamal
2006-08-15  0:36     ` Alexey Kuznetsov
2006-08-15  0:56       ` Herbert Xu
2006-08-15  2:46         ` jamal
2006-08-15  3:03           ` jamal [this message]
2006-08-15 11:17       ` Thomas Graf
2006-08-15 12:08         ` Hasso Tepper
2006-08-15 12:23           ` Thomas Graf
2006-08-16  2:58             ` Herbert Xu
2006-08-16  3:04               ` Herbert Xu
2006-08-16 10:58               ` Thomas Graf
2006-08-16 11:03                 ` jamal
2006-08-16 11:12                 ` Herbert Xu
2006-08-16 11:39                   ` Herbert Xu
2006-08-16 12:04                     ` jamal
2006-08-16 12:08                       ` Herbert Xu
2006-08-16 12:08                       ` Thomas Graf
2006-08-16 12:36                         ` jamal
2006-08-16 13:04                           ` Alexey Kuznetsov
2006-08-16 13:11                             ` jamal
2006-08-16 12:13                     ` Thomas Graf
2006-08-16 11:40                   ` Thomas Graf
2006-08-16 11:57                     ` Herbert Xu
2006-08-16 12:05                       ` Thomas Graf
2006-08-16 12:08                         ` jamal
2006-08-16 12:54               ` Alexey Kuznetsov
2006-08-13 22:00 ` [PATCH 10/16] [IPv6] route: Convert route notifications " Thomas Graf
2006-08-13 22:00 ` [PATCH 11/16] [IPv6] link: Convert link " Thomas Graf
2006-08-13 22:00 ` [PATCH 12/16] [IPv6] prefix: Convert prefix " Thomas Graf
2006-08-13 22:00 ` [PATCH 13/16] [BRIDGE]: Convert " Thomas Graf
2006-08-13 22:00 ` [PATCH 14/16] [WIRELESS]: " Thomas Graf
2006-08-13 22:00 ` [PATCH 15/16] [NET] link: " Thomas Graf
2006-08-13 22:00 ` [PATCH 16/16] [RTNETLINK]: Unexport rtnl socket Thomas Graf
2006-08-15  7:38 ` [PATCHSET] rtnetlink notification rework 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=1155611014.6946.82.camel@jzny2 \
    --to=hadi@cyberus.ca \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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).