From: Jiri Pirko <jiri@resnulli.us>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Ido Schimmel <idosch@mellanox.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
"moderated list:ETHERNET BRIDGE"
<bridge@lists.linux-foundation.org>,
jiri@mellanox.com, andrew@lunn.ch, vivien.didelot@gmail.com
Subject: Re: [PATCH net-next 1/3] mlxsw: spectrum_switchdev: Remove getting PORT_BRIDGE_FLAGS
Date: Tue, 12 Feb 2019 09:55:58 +0100 [thread overview]
Message-ID: <20190212085558.GC2881@nanopsycho> (raw)
In-Reply-To: <20190211211749.19847-2-f.fainelli@gmail.com>
Mon, Feb 11, 2019 at 10:17:47PM CET, f.fainelli@gmail.com wrote:
>There is no code that will query the SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS
>attribute remove support for that.
>
>Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Acked-by: Jiri Pirko <jiri@mellanox.com>
next prev parent reply other threads:[~2019-02-12 9:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 21:17 [Bridge] [PATCH net-next 0/3] Remove getting SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS Florian Fainelli
2019-02-11 21:17 ` Florian Fainelli
2019-02-11 21:17 ` [Bridge] [PATCH net-next 1/3] mlxsw: spectrum_switchdev: Remove getting PORT_BRIDGE_FLAGS Florian Fainelli
2019-02-11 21:17 ` Florian Fainelli
2019-02-12 8:55 ` Jiri Pirko [this message]
2019-02-12 12:18 ` [Bridge] " Ido Schimmel
2019-02-12 12:18 ` Ido Schimmel
2019-02-11 21:17 ` [Bridge] [PATCH net-next 2/3] rocker: " Florian Fainelli
2019-02-11 21:17 ` Florian Fainelli
2019-02-12 8:56 ` Jiri Pirko
2019-02-11 21:17 ` [Bridge] [PATCH net-next 3/3] staging: fsl-dpaa2: ethsw: " Florian Fainelli
2019-02-11 21:17 ` Florian Fainelli
2019-02-12 7:28 ` [Bridge] " Greg KH
2019-02-12 7:28 ` Greg KH
2019-02-12 8:56 ` Jiri Pirko
2019-02-12 8:55 ` [PATCH net-next 0/3] Remove getting SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS Jiri Pirko
2019-02-12 17:50 ` [Bridge] " David Miller
2019-02-12 17:50 ` David Miller
2019-02-12 17:54 ` [Bridge] " Florian Fainelli
2019-02-12 17:54 ` Florian Fainelli
2019-02-12 21:35 ` [Bridge] " Florian Fainelli
2019-02-12 21:35 ` Florian Fainelli
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=20190212085558.GC2881@nanopsycho \
--to=jiri@resnulli.us \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=f.fainelli@gmail.com \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@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.