From: Stephen Hemminger <shemminger@osdl.org>
To: Thomas Graham <lkthomas@sml.dyndns.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, bridge@osdl.org
Subject: Re: Bridge-utils update for 2.6 ?
Date: Thu, 08 Jan 2004 20:43:03 -0800 [thread overview]
Message-ID: <3FFE3157.9030307@osdl.org> (raw)
In-Reply-To: <1059.192.168.0.97.1073611363.squirrel@sml.dyndns.org>
Thomas Graham wrote:
> does anyone know if there have any new update patch for Bridge-utils on
> 2.6.0kernel ?!
> http://bridge.sourceforge.net/download.html <--- this is the web site
Existing 2.4 kernels work on 2.6, no API changes.
I am planning on an update later when STP is moved out of the kernel.
next prev parent reply other threads:[~2004-01-09 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 1:22 Bridge-utils update for 2.6 ? Thomas Graham
2004-01-09 4:43 ` Stephen Hemminger [this message]
2004-01-09 10:03 ` Thomas Graham
2004-01-09 10:04 ` Catalin BOIE
2004-01-09 10:51 ` Thomas Graham
2004-01-09 11:58 ` Catalin BOIE
2004-01-09 17:17 ` Stephen Hemminger
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=3FFE3157.9030307@osdl.org \
--to=shemminger@osdl.org \
--cc=bridge@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkthomas@sml.dyndns.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