netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Satendra..." <satendra.pratap@gmail.com>
To: David Lamparter <equinox@diac24.net>
Cc: Jens Osterkamp <jens@linux.vnet.ibm.com>, netdev@vger.kernel.org
Subject: Re: 802.1ad on linux
Date: Fri, 29 Jul 2011 11:24:21 +0530	[thread overview]
Message-ID: <CAChS5kPtnG_adb5DMdX5D+QogAQ57_2X+d4Lo3tToHS0wjaiNw@mail.gmail.com> (raw)
In-Reply-To: <20110728124830.GA2144046@jupiter.n2.diac24.net>

Thanks Jens and David.
David, could you give little idea about how you are testing your changes?
I mean is there any test suite used (may be third party) ?

On 28 July 2011 18:18, David Lamparter <equinox@diac24.net> wrote:
> On Thu, Jul 28, 2011 at 01:21:46PM +0200, Jens Osterkamp wrote:
>> On Thursday 28 July 2011, Satendra... wrote:
>> > Hi,
>> >
>> > Does linux kernel has support for 802.1ad ? if yes could u plz mention
>> > the version?
>>
>> No, but David Lamparter has just recently posted patches which implement this.
>>
>> http://marc.info/?l=linux-netdev&m=131093613717022&w=2
>>
>> They work fine for me on top of net-next. I had to add EXPORT_SYMBOL for
>> vlan_untag and vlan_do_receive to be able to build as a module.
>> You will need his patch for iproute2 as well to be able to create 802.1ad
>> VLAN devices.
>
> I will be rebasing them onto current net-next HEAD this weekend. With
> the VLAN cleanup in, some bits changed; I'll also do some reordering to
> fix those symbols.
>
>
> -David
>
>

      reply	other threads:[~2011-07-29  5:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28  9:44 802.1ad on linux Satendra...
2011-07-28 11:21 ` Jens Osterkamp
2011-07-28 12:48   ` David Lamparter
2011-07-29  5:54     ` Satendra... [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=CAChS5kPtnG_adb5DMdX5D+QogAQ57_2X+d4Lo3tToHS0wjaiNw@mail.gmail.com \
    --to=satendra.pratap@gmail.com \
    --cc=equinox@diac24.net \
    --cc=jens@linux.vnet.ibm.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).