From: yzhu1 <Yanjun.Zhu@windriver.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
"Wu, Kuaikuai" <Kuaikuai.Wu@windriver.com>,
"Tao, Yue" <Yue.Tao@windriver.com>
Subject: Re: If bridge have no sub-interfaces, it's status may be still with 'RUNNING'
Date: Wed, 25 Feb 2015 10:55:53 +0800 [thread overview]
Message-ID: <54ED39B9.4090107@windriver.com> (raw)
In-Reply-To: <E66F6C44A7A6EA49ABFC80EA526506DF65AEAEB3@ALA-MBB.corp.ad.wrs.com>
Hi, Stephen && David
Any update?
Zhu Yanjun
On 02/18/2015 12:14 AM, Zhu, Yanjun wrote:
> Hi, all
>
> We should make it compatible. So I made a patch to turn on carrier on this bridge interface when the last sub interface is removed.
>
> Hi, David
>
> Please make tests with this latest patch. Thanks a lot.
>
> Best Regards!
> Zhu Yanjun
> ________________________________________
> From: Stephen Hemminger [stephen@networkplumber.org]
> Sent: Monday, February 16, 2015 8:51 AM
> To: David Ahern
> Cc: Zhu, Yanjun; netdev; Wu, Kuaikuai; Tao, Yue
> Subject: Re: If bridge have no sub-interfaces, it's status may be still with 'RUNNING'
>
> Originally bridge code would start with carrier off,
> but there were users using bridge as a form of dummy device
> and this broke them. Therefore it was decided (like 5 yrs ago),
> that bridge should start with carrier on.
next prev parent reply other threads:[~2015-02-25 2:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 9:57 If bridge have no sub-interfaces, it's status may be still with 'RUNNING' yzhu1
2015-02-13 10:00 ` yzhu1
2015-02-13 18:30 ` Stephen Hemminger
2015-02-15 7:49 ` Wu, Kuaikuai
2015-02-16 4:55 ` yzhu1
2015-02-16 15:47 ` David Ahern
2015-02-16 16:51 ` Stephen Hemminger
2015-02-17 16:14 ` Zhu, Yanjun
2015-02-25 2:55 ` yzhu1 [this message]
2015-02-25 4:23 ` David Ahern
2015-02-25 5:29 ` yzhu1
2015-02-16 16:52 ` Stephen Hemminger
2015-03-10 6:07 ` yzhu1
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=54ED39B9.4090107@windriver.com \
--to=yanjun.zhu@windriver.com \
--cc=Kuaikuai.Wu@windriver.com \
--cc=Yue.Tao@windriver.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.