[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEP_g=9V=5zHqwz710TSuRSqTdo1kqkKF2VEEV6K3Tv1zupegg@mail.gmail.com>
Date: Tue, 20 Sep 2011 14:27:29 -0700
From: Jesse Gross <jesse@...ira.com>
To: Matt Carlson <mcarlson@...adcom.com>
Cc: Kasper Pedersen <kernel@...perkp.dk>,
Michael Chan <mchan@...adcom.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tg3: fix VLAN tagging regression
On Tue, Sep 20, 2011 at 2:09 PM, Matt Carlson <mcarlson@...adcom.com> wrote:
> On Tue, Sep 20, 2011 at 01:48:56PM -0700, Kasper Pedersen wrote:
>> commit 92cd3a17ce9c719abb4c28dee3438e0c641f8de4
>> tg3: Simplify tx bd assignments
>>
>> broke VLAN tagging on outbound packets.
>> It ifdef'ed BCM_KERNEL_SUPPORTS_8021Q, but this
>> is not set anywhere. So vlan never gets set, and
>> all packets are sent with vlan=0.
>>
>> Change to use the CONFIG_VLAN_xxx defines instead.
>> Tested on BCM5721 rev 11.
>>
>> Signed-off-by: Kasper Pedersen <kernel@...perkp.dk>
>
> Yes. This is correct.
>
> Acked-by: Matt Carlson <mcarlson@...adcom.com>
Actually, please don't do this. Those config #define's refer to the
802.1q module that creates vlan devices only. The rest of the network
stack has code for dealing with vlan packets that is not protected by
config guards, so there's no reason that drivers should be. The
correct thing to do here is just drop the test altogether and
unconditionally include the code.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists