[PATCH stable 5.16+ 0/3] backported Realtek DSA driver fixes for 5.16 and 5.17

Alvin Šipraga posted 3 patches 4 years ago
drivers/net/dsa/realtek/Kconfig            |  1 +
drivers/net/dsa/realtek/realtek-smi-core.c | 48 +++++++++++++++++--
drivers/net/dsa/realtek/realtek-smi-core.h |  2 +
drivers/net/dsa/realtek/rtl8365mb.c        | 54 +++++++++++++---------
4 files changed, 81 insertions(+), 24 deletions(-)
[PATCH stable 5.16+ 0/3] backported Realtek DSA driver fixes for 5.16 and 5.17
Posted by Alvin Šipraga 4 years ago
From: Alvin Šipraga <alsi@bang-olufsen.dk>

These fixes can be applied to both 5.16 and 5.17 - the subtree of
drivers/net/dsa/realtek is identical save for a few unrelated places.

The main backporting effort was to remove some parts of the patches
which touched the newly introduced MDIO interface, which was introduced
in the 5.18 development cycle, and to work around a mass-rename of a
single variable (smi -> priv). Regrettably this rename will make future
stable backports equally tedious and hard to automate.

Please let me know if you would like me to send the series again for
5.17.

Thanks!


Alvin Šipraga (3):
  net: dsa: realtek: allow subdrivers to externally lock regmap
  net: dsa: realtek: rtl8365mb: serialize indirect PHY register access
  net: dsa: realtek: make interface drivers depend on OF

 drivers/net/dsa/realtek/Kconfig            |  1 +
 drivers/net/dsa/realtek/realtek-smi-core.c | 48 +++++++++++++++++--
 drivers/net/dsa/realtek/realtek-smi-core.h |  2 +
 drivers/net/dsa/realtek/rtl8365mb.c        | 54 +++++++++++++---------
 4 files changed, 81 insertions(+), 24 deletions(-)

-- 
2.35.1

Re: [PATCH stable 5.16+ 0/3] backported Realtek DSA driver fixes for 5.16 and 5.17
Posted by Greg Kroah-Hartman 4 years ago
On Tue, Apr 12, 2022 at 07:32:49PM +0200, Alvin Šipraga wrote:
> From: Alvin Šipraga <alsi@bang-olufsen.dk>
> 
> These fixes can be applied to both 5.16 and 5.17 - the subtree of
> drivers/net/dsa/realtek is identical save for a few unrelated places.
> 
> The main backporting effort was to remove some parts of the patches
> which touched the newly introduced MDIO interface, which was introduced
> in the 5.18 development cycle, and to work around a mass-rename of a
> single variable (smi -> priv). Regrettably this rename will make future
> stable backports equally tedious and hard to automate.
> 
> Please let me know if you would like me to send the series again for
> 5.17.

5.16 is now end-of-life, but I've queued these up for 5.17 now, thanks!

greg k-h