Netdev List
 help / color / mirror / Atom feed
From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: Andrew Lunn <andrew@lunn.ch>, Javen Xu <javen_xu@realsil.com.cn>
Cc: "Heiner Kallweit" <hkallweit1@gmail.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Mateusz Jończyk" <mat.jonczyk@o2.pl>,
	stable@vger.kernel.org
Subject: [PATCH] net: phy: realtek: fix listing of sysfs directory tree
Date: Sun, 15 Nov 2026 22:40:45 +0100	[thread overview]
Message-ID: <20261115214045.3704-1-mat.jonczyk@o2.pl> (raw)

On git master, listing the contents of sysfs produces an error:

	root@mateusz-debian:/sys# LANG=C find -iname foobar
	find: './module/realtek/drivers': Input/output error
	root@mateusz-debian:/sys# LANG=C ls -1 ./module/realtek/drivers
	ls: reading directory './module/realtek/drivers': Input/output error
	'mdio_bus:Generic FE-GE Realtek PHY'
	'mdio_bus:RTL8201CP Ethernet'
	'mdio_bus:RTL8201F Fast Ethernet'
	'mdio_bus:RTL8208 Fast Ethernet'
	'mdio_bus:RTL8211B Gigabit Ethernet'
	[...]

Investigation shows that the forward slash in the driver name is the
culprit. Fix it.

Cc: stable@vger.kernel.org
Fixes: f0667918d5fc ("net: phy: realtek: add support for RTL8261D")
Signed-off-by: Mateusz Jończyk <mat.jonczyk@o2.pl>
---
 drivers/net/phy/realtek/realtek_main.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/phy/realtek/realtek_main.c b/drivers/net/phy/realtek/realtek_main.c
index ca2d515b77b3..a39ad18382f2 100644
--- a/drivers/net/phy/realtek/realtek_main.c
+++ b/drivers/net/phy/realtek/realtek_main.c
@@ -3483,7 +3483,7 @@ static struct phy_driver realtek_drvs[] = {
 		.write_mmd	= genphy_write_mmd_unsupported,
 	}, {
 		PHY_ID_MATCH_EXACT(RTL_8261C_CG),
-		.name			= "Realtek RTL8261C/D 10Gbps PHY",
+		.name			= "Realtek RTL8261C_RTL8261D 10Gbps PHY",
 		.probe			= rtl8261x_probe,
 		.config_init		= rtl8261x_config_init,
 		.get_features		= rtl8261x_get_features,
-- 
2.47.3


                 reply	other threads:[~2026-11-15 21:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261115214045.3704-1-mat.jonczyk@o2.pl \
    --to=mat.jonczyk@o2.pl \
    --cc=andrew@lunn.ch \
    --cc=hkallweit1@gmail.com \
    --cc=javen_xu@realsil.com.cn \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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