public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: adobriyan@gmail.com
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org,
	containers@osdl.org
Subject: Re: [PATCH 1/2] netns bridge: allow bridges in netns!
Date: Mon, 08 Sep 2008 16:20:28 -0700 (PDT)	[thread overview]
Message-ID: <20080908.162028.16064976.davem@davemloft.net> (raw)
In-Reply-To: <20080906064304.GA7810@x200.localdomain>

From: Alexey Dobriyan <adobriyan@gmail.com>
Date: Sat, 6 Sep 2008 10:43:05 +0400

> Bridge as netdevice doesn't cross netns boundaries.
> 
> Bridge ports and bridge itself live in same netns.
> 
> Notifiers are fixed.
> 
> netns propagated from userspace socket for setup and teardown.
> 
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>

Applied to net-next-2.6

  reply	other threads:[~2008-09-08 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06  6:43 [PATCH 1/2] netns bridge: allow bridges in netns! Alexey Dobriyan
2008-09-08 23:20 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-21 22:15 adobriyan

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=20080908.162028.16064976.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=adobriyan@gmail.com \
    --cc=containers@osdl.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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