From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, idosch@mellanox.com,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
oss-drivers@netronome.com, devel@driverdev.osuosl.org,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next v4 00/12] net: Introduce ndo_get_port_parent_id()
Date: Wed, 06 Feb 2019 13:50:50 -0800 (PST) [thread overview]
Message-ID: <20190206.135050.939253959263316807.davem@davemloft.net> (raw)
In-Reply-To: <20190206174546.23597-1-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Wed, 6 Feb 2019 09:45:34 -0800
> Based on discussion with Ido and feedback from Jakub there are clearly
> two classes of users that implement SWITCHDEV_ATTR_ID_PORT_PARENT_ID:
>
> - PF/VF drivers which typically only implement return the port's parent
> ID, yet have to implement switchdev_port_attr_get() just for that
>
> - Ethernet switch drivers: mlxsw, ocelot, DSA, etc. which implement more
> attributes which we want to be able to eventually veto in the context
> of the caller, thus making them candidates for using a blocking notifier
> chain
>
> Changes in v4:
..
Series applied, thanks Florian.
I'll push this out to net-next after my build tests complete.
next prev parent reply other threads:[~2019-02-06 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 17:45 [PATCH net-next v4 00/12] net: Introduce ndo_get_port_parent_id() Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 01/12] " Florian Fainelli
2019-02-06 19:10 ` Ido Schimmel
2019-02-06 17:45 ` [PATCH net-next v4 02/12] bnxt: Implement ndo_get_port_parent_id() Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 03/12] liquidio: " Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 04/12] net/mlx5e: " Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 05/12] mlxsw: " Florian Fainelli
2019-02-06 19:04 ` Ido Schimmel
2019-02-06 17:45 ` [PATCH net-next v4 06/12] mscc: ocelot: " Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 07/12] nfp: " Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 08/12] rocker: " Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 09/12] netdevsim: " Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 10/12] staging: fsl-dpaa2: ethsw: " Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 11/12] net: dsa: " Florian Fainelli
2019-02-06 17:45 ` [PATCH net-next v4 12/12] net: Get rid of SWITCHDEV_ATTR_ID_PORT_PARENT_ID Florian Fainelli
2019-02-06 19:10 ` Ido Schimmel
2019-02-06 21:50 ` David Miller [this message]
2019-02-06 22:18 ` [PATCH net-next v4 00/12] net: Introduce ndo_get_port_parent_id() 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=20190206.135050.939253959263316807.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=f.fainelli@gmail.com \
--cc=idosch@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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 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).