From: Stephen Hemminger <shemminger@vyatta.com>
To: Ken-ichirou MATSUZAWA <chamas@h4.dion.ne.jp>
Cc: Ken-ichirou MATSUZAWA <chamas@h4.dion.ne.jp>, netdev@vger.kernel.org
Subject: Re: [PATCH] don't touch bridge sysfs in container.
Date: Thu, 9 Jul 2009 14:23:17 -0700 [thread overview]
Message-ID: <20090709142317.542c51a4@nehalam> (raw)
In-Reply-To: <877hyicf4x.wl%chamas@h4.dion.ne.jp>
On Thu, 09 Jul 2009 19:41:34 +0900
Ken-ichirou MATSUZAWA <chamas@h4.dion.ne.jp> wrote:
> Hello,
>
> At Wed, 8 Jul 2009 09:33:20 -0700,
> Stephen Hemminger wrote:
>
> > There is a per netns sysfs interface, it should be changed to use that.
>
> Sorry, I can see only:
>
> - add netns suffix was disagreed
> - tagged sysfs may not be merged
Without tagged sysfs, how could bridge interface work in other containers?
--
next prev parent reply other threads:[~2009-07-09 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 11:56 [PATCH] don't touch bridge sysfs in container Ken-ichirou MATSUZAWA
2009-07-08 16:33 ` Stephen Hemminger
2009-07-09 10:41 ` Ken-ichirou MATSUZAWA
2009-07-09 21:23 ` Stephen Hemminger [this message]
2009-07-11 3:59 ` Ken-ichirou MATSUZAWA
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=20090709142317.542c51a4@nehalam \
--to=shemminger@vyatta.com \
--cc=chamas@h4.dion.ne.jp \
--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).