From: Vladimir Oltean <olteanv@gmail.com>
To: davem@davemloft.net
Cc: horatiu.vultur@microchip.com, alexandre.belloni@bootlin.com,
andrew@lunn.ch, f.fainelli@gmail.com, vivien.didelot@gmail.com,
joergen.andreasen@microchip.com, allan.nielsen@microchip.com,
alexandru.marginean@nxp.com, claudiu.manoil@nxp.com,
xiaoliang.yang_1@nxp.com, yangbo.lu@nxp.com,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: [PATCH v2 net-next 0/2] Allow unknown unicast traffic to CPU for Felix DSA
Date: Mon, 24 Feb 2020 23:34:56 +0200 [thread overview]
Message-ID: <20200224213458.32451-1-olteanv@gmail.com> (raw)
From: Vladimir Oltean <vladimir.oltean@nxp.com>
This is the continuation of the previous "[PATCH net-next] net: mscc:
ocelot: Workaround to allow traffic to CPU in standalone mode":
https://www.spinics.net/lists/netdev/msg631067.html
Following the feedback received from Allan Nielsen, the Ocelot and Felix
drivers were made to use the CPU port module in the same way (patch 1),
and Felix was made to additionally allow unknown unicast frames towards
the CPU port module (patch 2).
Vladimir Oltean (2):
net: mscc: ocelot: eliminate confusion between CPU and NPI port
net: dsa: felix: Allow unknown unicast traffic towards the CPU port
module
drivers/net/dsa/ocelot/felix.c | 16 ++++--
drivers/net/ethernet/mscc/ocelot.c | 62 +++++++++++++---------
drivers/net/ethernet/mscc/ocelot.h | 10 ----
drivers/net/ethernet/mscc/ocelot_board.c | 5 +-
include/soc/mscc/ocelot.h | 67 ++++++++++++++++++++++--
net/dsa/tag_ocelot.c | 3 +-
6 files changed, 117 insertions(+), 46 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-24 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 21:34 Vladimir Oltean [this message]
2020-02-24 21:34 ` [PATCH v2 net-next 1/2] net: mscc: ocelot: eliminate confusion between CPU and NPI port Vladimir Oltean
2020-02-25 12:55 ` Allan W. Nielsen
2020-02-24 21:34 ` [PATCH v2 net-next 2/2] net: dsa: felix: Allow unknown unicast traffic towards the CPU port module Vladimir Oltean
2020-02-25 13:01 ` Allan W. Nielsen
2020-02-25 13:02 ` [PATCH v2 net-next 0/2] Allow unknown unicast traffic to CPU for Felix DSA Allan W. Nielsen
2020-02-25 13:08 ` Vladimir Oltean
2020-02-25 13:37 ` Andrew Lunn
2020-02-25 13:57 ` Vladimir Oltean
2020-02-25 13:43 ` Allan W. Nielsen
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=20200224213458.32451-1-olteanv@gmail.com \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandru.marginean@nxp.com \
--cc=allan.nielsen@microchip.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=joergen.andreasen@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=yangbo.lu@nxp.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).