From: "Marek Behún" <kabel@kernel.org>
To: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Marek Behún" <kabel@kernel.org>
Subject: [PATCH net v2 0/6] dsa: mv88e6xxx: Topaz fixes
Date: Thu, 1 Jul 2021 00:22:25 +0200 [thread overview]
Message-ID: <20210630222231.2297-1-kabel@kernel.org> (raw)
In-Reply-To: <20210630174308.31831-1-kabel@kernel.org>
Hello,
here comes some fixes for the Topaz family (Marvell 88E6141 / 88E6341)
which I found out about when I compared the Topaz' operations
structure with that one of Peridot (6390).
This is v2. In v1, I accidentally sent patches generated from wrong
branch and the 5th patch does not contain a necessary change in
serdes.c.
Changes from v1:
- the fifth patch, "enable SerDes RX stats for Topaz", needs another
change in serdes.c
- Andrew's Reviewed-by to 1,2,3,4 and 6
Marek Behún (6):
net: dsa: mv88e6xxx: enable .port_set_policy() on Topaz
net: dsa: mv88e6xxx: use correct .stats_set_histogram() on Topaz
net: dsa: mv88e6xxx: enable .rmu_disable() on Topaz
net: dsa: mv88e6xxx: enable devlink ATU hash param for Topaz
net: dsa: mv88e6xxx: enable SerDes RX stats for Topaz
net: dsa: mv88e6xxx: enable SerDes PCS register dump via ethtool -d on
Topaz
drivers/net/dsa/mv88e6xxx/chip.c | 22 ++++++++++++++++++++--
drivers/net/dsa/mv88e6xxx/serdes.c | 6 +++---
2 files changed, 23 insertions(+), 5 deletions(-)
--
2.31.1
next prev parent reply other threads:[~2021-06-30 22:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 17:43 [PATCH net 0/6] dsa: mv88e6xxx: Topaz fixes Marek Behún
2021-06-30 17:43 ` [PATCH net 1/6] net: dsa: mv88e6xxx: enable .port_set_policy() on Topaz Marek Behún
2021-06-30 20:02 ` Andrew Lunn
2021-06-30 17:43 ` [PATCH net 2/6] net: dsa: mv88e6xxx: use correct .stats_set_histogram() " Marek Behún
2021-06-30 20:03 ` Andrew Lunn
2021-06-30 17:43 ` [PATCH net 3/6] net: dsa: mv88e6xxx: enable .rmu_disable() " Marek Behún
2021-06-30 20:07 ` Andrew Lunn
2021-06-30 17:43 ` [PATCH net 4/6] net: dsa: mv88e6xxx: enable devlink ATU hash param for Topaz Marek Behún
2021-06-30 20:08 ` Andrew Lunn
2021-06-30 17:43 ` [PATCH net 5/6] net: dsa: mv88e6xxx: enable SerDes RX stats " Marek Behún
2021-06-30 20:08 ` Andrew Lunn
2021-06-30 22:15 ` Marek Behún
2021-06-30 17:43 ` [PATCH net 6/6] net: dsa: mv88e6xxx: enable SerDes PCS register dump via ethtool -d on Topaz Marek Behún
2021-06-30 20:10 ` Andrew Lunn
2021-06-30 22:22 ` Marek Behún [this message]
2021-06-30 22:22 ` [PATCH net v2 1/6] net: dsa: mv88e6xxx: enable .port_set_policy() " Marek Behún
2021-06-30 22:22 ` [PATCH net v2 2/6] net: dsa: mv88e6xxx: use correct .stats_set_histogram() " Marek Behún
2021-06-30 22:22 ` [PATCH net v2 3/6] net: dsa: mv88e6xxx: enable .rmu_disable() " Marek Behún
2021-06-30 22:22 ` [PATCH net v2 4/6] net: dsa: mv88e6xxx: enable devlink ATU hash param for Topaz Marek Behún
2021-06-30 22:22 ` [PATCH net v2 5/6] net: dsa: mv88e6xxx: enable SerDes RX stats " Marek Behún
2021-06-30 22:22 ` [PATCH net v2 6/6] net: dsa: mv88e6xxx: enable SerDes PCS register dump via ethtool -d on Topaz 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=20210630222231.2297-1-kabel@kernel.org \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).