Ethernet Bridge development
 help / color / mirror / Atom feed
From: Mark Ruijter <bridge@siennax.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Bridge code enhancement (link state detection) and bug fix. (patches included).
Date: Sat, 17 Jul 2004 21:31:56 +0200	[thread overview]
Message-ID: <40F97EAC.5020605@siennax.com> (raw)
In-Reply-To: <20040716162855.52d91672@dell_ss3.pdx.osdl.net>


> 
> 
> Could you split out the link state monitoring, and look at bonding to see
> how they are doing it?

Yes, no problem.

> 
> I have a fix for vlan code that passes MII and ethtool requests from the virtual
> to physical device, so the bridge code wouldn't need to the hack about root device.
> 

I'll change the code so it doesn't include the root device hack anymore.

Mark.


  reply	other threads:[~2004-07-17 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 18:57 [Bridge] Bridge code enhancement (link state detection) and bug fix. (patches included) Mark Ruijter
2004-06-17 20:28 ` Stephen Hemminger
2004-06-17 21:08   ` Mark Ruijter
2004-07-16 23:28 ` Stephen Hemminger
2004-07-17 19:31   ` Mark Ruijter [this message]
2004-07-20 11:24   ` Mark Ruijter

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=40F97EAC.5020605@siennax.com \
    --to=bridge@siennax.com \
    --cc=bridge@lists.osdl.org \
    --cc=shemminger@osdl.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