All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] drivers/net: add 6WIND SHULTI support
Date: Wed, 27 Apr 2016 11:50:42 +0200	[thread overview]
Message-ID: <20160427095042.GA1962@nanopsycho.orion> (raw)
In-Reply-To: <1461749838-4613-1-git-send-email-nicolas.dichtel@6wind.com>

Wed, Apr 27, 2016 at 11:37:18AM CEST, nicolas.dichtel@6wind.com wrote:
>This patch adds the support of the 6WIND SHULTI switch. It is a software
>switch doing L2 forwarding.
>
>This first version implements the minimum needed to get the device working.
>It also implements, via switchdev and rtnetlink, bridge forwarding offload,
>including FDB static entries, FDB learning and FDB ageing.

I have to review this more closely, but at the first glance, this is
triggering a TRAMPOLINE ALERT!

Would you please share more description about this "driver". What is the
purpose, what are benefits, usecases, etc.

Thanks!

  reply	other threads:[~2016-04-27  9:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27  9:37 [PATCH net-next] drivers/net: add 6WIND SHULTI support Nicolas Dichtel
2016-04-27  9:50 ` Jiri Pirko [this message]
2016-04-27  9:56 ` Florian Westphal
2016-04-27 15:14   ` Jiri Pirko
2016-04-27 15:38     ` Nicolas Dichtel
2016-04-27 15:54       ` Jiri Pirko
2016-04-27 16:55     ` David Miller
2016-04-27 17:07       ` Stephen Hemminger
2016-04-28 12:00         ` Nicolas Dichtel
2016-04-28 11:59       ` Nicolas Dichtel
2016-04-28 14:05         ` Or Gerlitz
2016-04-28 15:54         ` David Miller
2016-04-29  8:48           ` Nicolas Dichtel
2016-05-01 15:27             ` Jiri Pirko
2016-05-01 19:53           ` Jiri Pirko
2016-05-01 15:24         ` Jiri Pirko
2016-04-27 16:34 ` David Miller

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=20160427095042.GA1962@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.