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: Fri, 13 Mar 2015 06:25:24 -0700	[thread overview]
Message-ID: <5502E544.7030003@cumulusnetworks.com> (raw)
In-Reply-To: <20150313.001007.65274068513753002.davem@davemloft.net>

On 3/12/15, 9:10 PM, David Miller wrote:
> From: roopa@cumulusnetworks.com
> Date: Thu, 12 Mar 2015 17:29:55 -0700
>
>> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>>
>> This series moves bridge stp update api to follow the setlink/dellink
>> apis to propagate stp state updates to switch ports on stacked netdevs
>>
>> v1 -> v2:
>> 	fix comment
>> 	add CONFIG_NET_SWITCHDEV checks
>>
>> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
> Can't we just do this stacked device traveral transparently?
>
> That seems much cleaner to me.
David, if you mean not touch bond and team but have the switchdev api do 
it transparently, yes, i had it that way initially.
And i do liked it that way as well. But the feedback i received (during 
the initial introduction of this for setlink/dellink) was to make it 
explicit for each master.

Thanks,
Roopa

  reply	other threads:[~2015-03-13 13:25 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 [this message]
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
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=5502E544.7030003@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.