netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, ebiederm@xmission.com
Subject: Re: [PATCH] net: explain netns notifiers a little better
Date: Mon, 20 Jul 2009 08:04:09 -0700 (PDT)	[thread overview]
Message-ID: <20090720.080409.248628533.davem@davemloft.net> (raw)
In-Reply-To: <1247674594.10754.20.camel@johannes.local>

From: Johannes Berg <johannes@sipsolutions.net>
Date: Wed, 15 Jul 2009 18:16:34 +0200

> Eric explained this to me -- and afterwards the comment
> made sense, but not before. Add the the critical point
> about interfaces having to be gone from the netns before
> subsys notifiers are called.
> 
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>

Applied to net-next-2.6

      reply	other threads:[~2009-07-20 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 16:16 [PATCH] net: explain netns notifiers a little better Johannes Berg
2009-07-20 15:04 ` David Miller [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=20090720.080409.248628533.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=johannes@sipsolutions.net \
    --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).