From: Raju Rangoju <Raju.Rangoju@amd.com>
To: <netdev@vger.kernel.org>
Cc: <pabeni@redhat.com>, <kuba@kernel.org>, <edumazet@google.com>,
<davem@davemloft.net>, <andrew+netdev@lunn.ch>,
<Shyam-sundar.S-k@amd.com>, Raju Rangoju <Raju.Rangoju@amd.com>
Subject: [PATCH net-next v2 0/4] amd-xgbe: introduce support for ethtool selftests
Date: Fri, 17 Oct 2025 12:17:00 +0530 [thread overview]
Message-ID: <20251017064704.3911798-1-Raju.Rangoju@amd.com> (raw)
This patch series introduces support for ethtool selftests, which
helps in finding the misconfiguration of HW. Supports the following
tests:
- MAC loopback selftest
- PHY loopback selftest
- Split header selftest
- Jubmo frame selftest
Changes since v1:
- fix build warnings for s390 arch reported by kernel test robot
Raju Rangoju (4):
amd-xgbe: introduce support ethtool selftest
amd-xgbe: add ethtool phy selftest
amd-xgbe: add ethtool split header selftest
amd-xgbe: add ethtool jumbo frame selftest
drivers/net/ethernet/amd/xgbe/Makefile | 2 +-
drivers/net/ethernet/amd/xgbe/xgbe-dev.c | 2 +
drivers/net/ethernet/amd/xgbe/xgbe-ethtool.c | 7 +
drivers/net/ethernet/amd/xgbe/xgbe-selftest.c | 506 ++++++++++++++++++
drivers/net/ethernet/amd/xgbe/xgbe.h | 6 +
5 files changed, 522 insertions(+), 1 deletion(-)
create mode 100644 drivers/net/ethernet/amd/xgbe/xgbe-selftest.c
--
2.34.1
next reply other threads:[~2025-10-17 6:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 6:47 Raju Rangoju [this message]
2025-10-17 6:47 ` [PATCH net-next v2 1/4] amd-xgbe: introduce support ethtool selftest Raju Rangoju
2025-10-19 5:42 ` kernel test robot
2025-10-17 6:47 ` [PATCH net-next v2 2/4] amd-xgbe: add ethtool phy selftest Raju Rangoju
2025-10-18 3:33 ` kernel test robot
2025-10-17 6:47 ` [PATCH net-next v2 3/4] amd-xgbe: add ethtool split header selftest Raju Rangoju
2025-10-17 6:47 ` [PATCH net-next v2 4/4] amd-xgbe: add ethtool jumbo frame selftest Raju Rangoju
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=20251017064704.3911798-1-Raju.Rangoju@amd.com \
--to=raju.rangoju@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).