From: Egil Hjelmeland <egil.hjelmeland@zenitel.com>
To: <corbet@lwn.net>, <andrew@lunn.ch>,
<vivien.didelot@savoirfairelinux.com>, <f.fainelli@gmail.com>,
<davem@davemloft.net>, <kernel@pengutronix.de>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>
Cc: <egil.hjelmeland@zenitel.com>
Subject: [PATCH 00/13] net: dsa: lan9303: unicast offload, fdb,mdb,STP
Date: Mon, 24 Jul 2017 16:47:51 +0200 [thread overview]
Message-ID: <525d9bb74bfa42c1b7a54930e14cf5ea@nooslMX1.zenitelcss.com> (raw)
This series extends the LAN9303 3 port switch DSA driver. Highlights:
- Make the MDIO interface work
- Bridging: Unicast offload
- Bridging: Added fdb/mdb handling
- Bridging: STP support
- Documentation
The last three patches are workarounds due to current kernel limitations.
This is my first patches submitted to the kernel, so I am looking
forward to comments.
Egil Hjelmeland (13):
net: dsa: lan9303: Fixed MDIO interface
net: dsa: lan9303: Do not disable/enable switch fabric port 0 at
startup
net: dsa: lan9303: Refactor lan9303_enable_packet_processing()
net: dsa: lan9303: Added adjust_link() method
net: dsa: added dsa_net_device_to_dsa_port()
net: dsa: lan9303: added sysfs node swe_bcst_throt
net: dsa: lan9303: Added basic offloading of unicast traffic
net: dsa: lan9303: Added ALR/fdb/mdb handling
net: dsa: lan9303: Added Documentation/networking/dsa/lan9303.txt
net: dsa: lan9303: Only allocate 3 ports
net: dsa: lan9303: Added "alr_dump" sysfs port attribute
net: dsa: lan9303: Added "stp_enable" sysfs attribute
net: dsa: lan9303: lan9303_port_mdb_del remove port 0
Documentation/networking/dsa/lan9303.txt | 74 +++
drivers/net/dsa/lan9303-core.c | 811 ++++++++++++++++++++++++++++---
drivers/net/dsa/lan9303.h | 23 +
drivers/net/dsa/lan9303_i2c.c | 2 +
drivers/net/dsa/lan9303_mdio.c | 34 ++
include/net/dsa.h | 1 +
net/dsa/slave.c | 10 +
7 files changed, 885 insertions(+), 70 deletions(-)
create mode 100644 Documentation/networking/dsa/lan9303.txt
--
2.11.0
DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.
next reply other threads:[~2017-07-24 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 14:47 Egil Hjelmeland [this message]
2017-07-24 16:54 ` Florian Fainelli
2017-07-25 7:34 ` Egil Hjelmeland
2017-07-24 20:32 ` David Miller
2017-07-25 7:40 ` Egil Hjelmeland
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=525d9bb74bfa42c1b7a54930e14cf5ea@nooslMX1.zenitelcss.com \
--to=egil.hjelmeland@zenitel.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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
all inboxes | Powered by JetHome®