From: Ben Greear <greearb@candelatech.com>
To: olivier.crameri@epfl.ch
Cc: netdev@vger.kernel.org, Yoshio Turner <yoshiotu@hpl.hp.com>,
"Santos, Jose Renato G" <joserenato.santos@hp.com>,
"Janakiraman, John" <john.janakiraman@hp.com>
Subject: Re: Offloading features in VLAN interfaces
Date: Thu, 05 Oct 2006 09:25:39 -0700 [thread overview]
Message-ID: <45253203.8050805@candelatech.com> (raw)
In-Reply-To: <b54af0b00609291725t55ac0a84pf86525ef0a31f44e@mail.gmail.com>
Olivier Crameri wrote:
> Same thing but with the patch this time.
Since the VLAN device's features may also change in the handler,
shouldn't we check and generate a feature-change
event for the VLAN device(s) as well?
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2006-10-05 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 0:21 Offloading features in VLAN interfaces Olivier Crameri
2006-09-30 0:25 ` Olivier Crameri
2006-09-30 3:33 ` Stephen Hemminger
2006-10-05 16:25 ` Ben Greear [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=45253203.8050805@candelatech.com \
--to=greearb@candelatech.com \
--cc=john.janakiraman@hp.com \
--cc=joserenato.santos@hp.com \
--cc=netdev@vger.kernel.org \
--cc=olivier.crameri@epfl.ch \
--cc=yoshiotu@hpl.hp.com \
/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).