All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH net-next 0/6 v6] RTL8366(RB) cleanups part 1
Date: Sat, 25 Sep 2021 15:23:05 +0200	[thread overview]
Message-ID: <20210925132311.2040272-1-linus.walleij@linaro.org> (raw)

This is a first set of patches making the RTL8366RB work out of
the box with a default OpenWrt userspace.

We achieve bridge port isolation with the first patch, and the
next 5 patches removes the very weird VLAN set-up with one
VLAN with PVID per port that has been in this driver in all
vendor trees and in OpenWrt for years.

The switch is now managed the way a modern bridge/DSA switch
shall be managed.

After these patches are merged, I will send the next set which
adds new features, some which have circulated before.

ChangeLog v5->v6:
- Fix a dangling unused "ret" in patch 4.

ChangeLog v4->v5:
- Drop the patch disabling 4K VLAN.
- Drop the patch forcing VLAN0 untagged.
- Fix a semantic bug in the filer enablement code.

DENG Qingfang (1):
  net: dsa: rtl8366rb: Support bridge offloading

Linus Walleij (5):
  net: dsa: rtl8366: Drop custom VLAN set-up
  net: dsa: rtl8366rb: Rewrite weird VLAN filering enablement
  net: dsa: rtl8366rb: Fix off-by-one bug
  net: dsa: rtl8366: Fix a bug in deleting VLANs
  net: dsa: rtl8366: Drop and depromote pointless prints

 drivers/net/dsa/realtek-smi-core.h |   3 -
 drivers/net/dsa/rtl8366.c          |  96 ++---------------------
 drivers/net/dsa/rtl8366rb.c        | 122 ++++++++++++++++++++++++++---
 3 files changed, 117 insertions(+), 104 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-09-25 13:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-25 13:23 Linus Walleij [this message]
2021-09-25 13:23 ` [PATCH net-next 1/6 v6] net: dsa: rtl8366rb: Support bridge offloading Linus Walleij
2021-09-25 18:30   ` Vladimir Oltean
2021-09-25 13:23 ` [PATCH net-next 2/6 v6] net: dsa: rtl8366: Drop custom VLAN set-up Linus Walleij
2021-09-25 13:23 ` [PATCH net-next 3/6 v6] net: dsa: rtl8366rb: Rewrite weird VLAN filering enablement Linus Walleij
2021-09-25 17:12   ` Alvin Šipraga
2021-09-25 18:38     ` Vladimir Oltean
2021-09-25 22:44       ` Linus Walleij
2021-09-25 13:23 ` [PATCH net-next 4/6 v6] net: dsa: rtl8366rb: Fix off-by-one bug Linus Walleij
2021-09-25 17:16   ` Alvin Šipraga
2021-09-25 18:44   ` Vladimir Oltean
2021-09-26  2:32   ` Florian Fainelli
2021-09-25 13:23 ` [PATCH net-next 5/6 v6] net: dsa: rtl8366: Fix a bug in deleting VLANs Linus Walleij
2021-09-25 17:18   ` Alvin Šipraga
2021-09-25 18:50   ` Vladimir Oltean
2021-09-25 13:23 ` [PATCH net-next 6/6 v6] net: dsa: rtl8366: Drop and depromote pointless prints Linus Walleij
2021-09-25 17:19   ` Alvin Šipraga
2021-09-25 18:56   ` Vladimir Oltean
2021-09-25 22:54     ` Linus Walleij

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=20210925132311.2040272-1-linus.walleij@linaro.org \
    --to=linus.walleij@linaro.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --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.