From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Atis Elsts <atis.elsts@gmail.com>
Cc: Oleg Kutkov <elenbert@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Notifier chains bug ?
Date: Thu, 4 Mar 2010 18:08:07 +0800 [thread overview]
Message-ID: <2375c9f91003040208g1c66f1eft6c2c1044ed995c4e@mail.gmail.com> (raw)
In-Reply-To: <7f9bf5711003020755p653a0b8cq707e9b1e12b44c98@mail.gmail.com>
On Tue, Mar 2, 2010 at 11:55 PM, Atis Elsts <atis.elsts@gmail.com> wrote:
> I'm no expert, but IMHO for handling IP address changes you should use
> function register_inetaddr_notifier() to register you callback and
> then wait for NETDEV_UP and NETDEV_DOWN events.
>
Oh, I think you are right.
Btw, please don't drop Cc's.
Thanks.
prev parent reply other threads:[~2010-03-04 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B8C56F0.5090700@gmail.com>
[not found] ` <2375c9f91003011924k43f03649y5b4df405d6247a79@mail.gmail.com>
[not found] ` <5e9821061003012150y15e543cdkf6f23c3a7a47e4a3@mail.gmail.com>
2010-03-02 15:42 ` Notifier chains bug ? Américo Wang
2010-03-02 15:57 ` Atis Elsts
[not found] ` <7f9bf5711003020755p653a0b8cq707e9b1e12b44c98@mail.gmail.com>
2010-03-04 10:08 ` Américo 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=2375c9f91003040208g1c66f1eft6c2c1044ed995c4e@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=atis.elsts@gmail.com \
--cc=elenbert@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).