From: yzhu1 <Yanjun.Zhu@windriver.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <dsahern@gmail.com>
Subject: Re: [PATCH 1/1] bridge: turn off carrier when the bridge is created
Date: Wed, 11 Mar 2015 14:16:02 +0800 [thread overview]
Message-ID: <54FFDDA2.9070705@windriver.com> (raw)
In-Reply-To: <20150310222634.0e485497@urahara>
On 03/11/2015 01:26 PM, Stephen Hemminger wrote:
> On Wed, 11 Mar 2015 00:03:50 -0400 (EDT)
> David Miller <davem@davemloft.net> wrote:
>
>> From: yzhu1 <Yanjun.Zhu@windriver.com>
>> Date: Wed, 11 Mar 2015 10:39:53 +0800
>>
>>> Hi, Stephen && David
>>>
>>> Any comment?
>> Asking Stephen to look at this more times will not make him respond
>> any faster. I see your posting, he sees it, everyone sees it.
>>
>> If he's too busy to look into this, that's just the state of affairs
>> right now and you just need to be patient.
>>
>> Thanks.
> This was discussed and changed long ago (before git was used).
> Initially in 2.5 the bridge carrier was changed to work as you have
> described but this broke some user. Therefore it was decided that the
> best thing to do was keep the carrier always on for the bridge.
>
> You might be able to find the commit by using one of the kernel
> ancient history git trees. Kernel archeology is fun but
> too time consuming for me to bother with.
>
>
Thanks for your explanations.
Best Regards!
Zhu Yanjun
prev parent reply other threads:[~2015-03-11 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 7:09 [PATCH 0/1] bridge: turn off carrier when the bridge is created Zhu Yanjun
2015-03-10 7:09 ` [PATCH 1/1] " Zhu Yanjun
2015-03-11 2:39 ` yzhu1
2015-03-11 4:03 ` David Miller
2015-03-11 5:26 ` Stephen Hemminger
2015-03-11 5:29 ` David Miller
2015-03-11 6:16 ` yzhu1 [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=54FFDDA2.9070705@windriver.com \
--to=yanjun.zhu@windriver.com \
--cc=davem@davemloft.net \
--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 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).