From: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com, davem@davemloft.net
Subject: Re: [PATCH] [BRIDGE]
Date: Thu, 26 May 2005 08:49:23 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.62.0505260848300.7768@webhosting.rdsbv.ro> (raw)
In-Reply-To: <20050525091427.35621a21@dxpl.pdx.osdl.net>
On Wed, 25 May 2005, Stephen Hemminger wrote:
> On Tue, 24 May 2005 10:29:25 +0300 (EEST)
> "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro> wrote:
>
>> Hello!
>>
>> This patch set bridge device features using the common features of all
>> slaves. Also, it reacts to features change using ethtool on the slaves.
>>
>> This patch depends on NETDEV_FEAT_CHANGE.patch.
>>
>
> I will add it to the next set of patches for bridging. Hold off until
> 2.6.13
Thanks, Stephen!
P.S. This patch needs NETDEV_FEAT_CHANGE.patch. Do you include both?
---
Catalin(ux aka Dino) BOIE
catab at deuroconsult.ro
http://kernel.umbrella.ro/
prev parent reply other threads:[~2005-05-26 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 7:29 [PATCH] [BRIDGE] Catalin(ux aka Dino) BOIE
2005-05-25 16:14 ` Stephen Hemminger
2005-05-25 21:46 ` Stephen Hemminger
2005-05-26 6:36 ` Catalin(ux aka Dino) BOIE
2005-05-26 5:49 ` Catalin(ux aka Dino) BOIE [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=Pine.LNX.4.62.0505260848300.7768@webhosting.rdsbv.ro \
--to=util@deuroconsult.ro \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--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