From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: ogerlitz@voltaire.com, kaber@trash.net, fubar@us.ibm.com,
netdev@vger.kernel.org, eilong@broadcom.com, mchan@broadcom.com
Subject: Re: [PATCH net-next-2.6] bnx2: Update vlan_features
Date: Thu, 23 Jul 2009 10:59:32 -0700 (PDT) [thread overview]
Message-ID: <20090723.105932.249439810.davem@davemloft.net> (raw)
In-Reply-To: <4A685122.3090300@gmail.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 23 Jul 2009 14:01:38 +0200
> [PATCH net-next-2.6] bnx2: Update vlan_features
>
> In order to get full use of some advanced features of BNX2, we now need to
> fill dev->vlan_features.
>
> Patch successfully tested with vlan devices built on top of bonding.
> (bond0 : one bnx2 slave, one tg3 slave (not yet vlan_features enabled)
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Can I get some Broadcom ACKs for this?
Thanks.
next prev parent reply other threads:[~2009-07-23 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 13:00 zero features for a vlan over bond Or Gerlitz
2009-04-07 14:16 ` Jay Vosburgh
2009-04-07 22:16 ` Or Gerlitz
2009-04-16 14:11 ` zero features for a vlan over bond / vlan features Or Gerlitz
2009-04-23 23:47 ` Jay Vosburgh
2009-06-08 9:34 ` Or Gerlitz
2009-07-20 8:08 ` Or Gerlitz
2009-07-22 21:34 ` [PATCH net-next-2.6] bonding: propogate vlan_features to bonding master Jay Vosburgh
2009-07-23 6:03 ` Eric Dumazet
2009-07-23 7:24 ` Or Gerlitz
2009-07-23 8:29 ` [PATCH net-next-2.6] bnx2: Update vlan_features Eric Dumazet
2009-07-23 12:01 ` Eric Dumazet
2009-07-23 17:59 ` David Miller [this message]
2009-07-24 0:12 ` Michael Chan
2009-07-24 7:21 ` [PATCH net-next-2.6] bnx2x: Dont update vlan_features in bnx2x_set_tso() Eric Dumazet
2009-07-26 10:53 ` Eilon Greenstein
2009-07-27 2:49 ` David Miller
2009-07-27 2:50 ` [PATCH net-next-2.6] bnx2: Update vlan_features David Miller
2009-07-23 11:03 ` [PATCH net-next-2.6] bonding: propogate vlan_features to bonding master Patrick McHardy
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=20090723.105932.249439810.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=eric.dumazet@gmail.com \
--cc=fubar@us.ibm.com \
--cc=kaber@trash.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.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).