All of lore.kernel.org
 help / color / mirror / Atom feed
From: roopa <roopa@cumulusnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: sfeldma@gmail.com, jiri@resnulli.us, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] switchdev: support stp updates on stacked netdevices
Date: Mon, 16 Mar 2015 08:09:59 -0700	[thread overview]
Message-ID: <5506F247.2020701@cumulusnetworks.com> (raw)
In-Reply-To: <20150315.183312.401696632034773662.davem@davemloft.net>

On 3/15/15, 3:33 PM, David Miller wrote:
> From: Scott Feldman <sfeldma@gmail.com>
> Date: Sun, 15 Mar 2015 13:03:06 -0700
>
>> I'm proposing a simple, permissive solution, with a provision for an
>> out on a case-by-case basis.  Right now I don't see any reason to
>> special case any middle driver; just let STP state propagate down to
>> the port device.
> +1
ok. That was the path i had taken initially (see for getlink/setlink):
http://www.spinics.net/lists/netdev/msg313436.html

I have resubmitted the patch with rollback to transparently following 
lowerdevs.
My version also does not follow lowerdevs if NETIF_F_HW_SWITCH_OFFLOAD 
is not
set. And this is set on bonds and teams if any one of their lowerdevs 
have it currently.

thanks.

  reply	other threads:[~2015-03-16 15:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  0:29 [PATCH net-next v2 0/3] switchdev: support stp updates on stacked netdevices roopa
2015-03-13  4:10 ` David Miller
2015-03-13 13:25   ` roopa
2015-03-13 16:31     ` David Miller
2015-03-14  1:49       ` roopa
2015-03-15 16:56       ` Jiri Pirko
2015-03-15 22:30         ` David Miller
2015-03-15 18:08       ` Scott Feldman
2015-03-15 19:17         ` Jiri Pirko
2015-03-15 20:03           ` Scott Feldman
2015-03-15 22:33             ` David Miller
2015-03-16 15:09               ` roopa [this message]
2015-03-15 22:32           ` David Miller
2015-03-16  6:37             ` Jiri Pirko

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=5506F247.2020701@cumulusnetworks.com \
    --to=roopa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=sfeldma@gmail.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.