From: "Marek Behún" <kabel@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Vivien Didelot <vivien.didelot@gmail.com>,
Tobias Waldekranz <tobias@waldekranz.com>,
netdev@vger.kernel.org,
Fidan Aliyeva <fidan.aliyeva.ext@ericsson.com>
Cc: "Lev Olshvang" <lev_o@rad.com>, "Marek Behún" <kabel@kernel.org>
Subject: [PATCH net-next 0/5] Fixes for mv88e6xxx for 6320/6321 family
Date: Mon, 4 May 2026 17:32:22 +0200 [thread overview]
Message-ID: <20260504153227.1390546-1-kabel@kernel.org> (raw)
Five fixes for mv88e6xxx for 6320/6321 family, for net-next, without
Fixes tags, as per Andrew's request last year, see
https://lore.kernel.org/netdev/20250313134146.27087-1-kabel@kernel.org/
Marek Behún (5):
net: dsa: mv88e6xxx: fix number of g1 interrupts for 6320 family
net: dsa: mv88e6xxx: allow SPEED_200 for 6320 family on supported
ports
net: dsa: mv88e6xxx: define .pot_clear() for 6321
net: dsa: mv88e6xxx: enable .rmu_disable() for 6320 family
net: dsa: mv88e6xxx: enable devlink ATU hash param for 6320 family
drivers/net/dsa/mv88e6xxx/chip.c | 15 +++++++++++----
drivers/net/dsa/mv88e6xxx/port.c | 15 +++++++++++++++
drivers/net/dsa/mv88e6xxx/port.h | 2 ++
3 files changed, 28 insertions(+), 4 deletions(-)
--
2.53.0
next reply other threads:[~2026-05-04 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 15:32 Marek Behún [this message]
2026-05-04 15:32 ` [PATCH net-next 1/5] net: dsa: mv88e6xxx: fix number of g1 interrupts for 6320 family Marek Behún
2026-05-04 15:32 ` [PATCH net-next 2/5] net: dsa: mv88e6xxx: allow SPEED_200 for 6320 family on supported ports Marek Behún
2026-05-04 15:32 ` [PATCH net-next 3/5] net: dsa: mv88e6xxx: define .pot_clear() for 6321 Marek Behún
2026-05-04 15:32 ` [PATCH net-next 4/5] net: dsa: mv88e6xxx: enable .rmu_disable() for 6320 family Marek Behún
2026-05-04 15:32 ` [PATCH net-next 5/5] net: dsa: mv88e6xxx: enable devlink ATU hash param " Marek Behún
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=20260504153227.1390546-1-kabel@kernel.org \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=fidan.aliyeva.ext@ericsson.com \
--cc=lev_o@rad.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=tobias@waldekranz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox