From: Yajun Deng <yajun.deng@linux.dev>
To: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Yajun Deng <yajun.deng@linux.dev>
Subject: [PATCH net-next v2] net: mdio_bus: change the bus name to mdio
Date: Thu, 19 Dec 2024 18:04:54 +0800 [thread overview]
Message-ID: <20241219100454.1623211-1-yajun.deng@linux.dev> (raw)
Since all directories under the /sys/bus are bus, we don't need to add a
bus suffix to mdio.
This is the only one directory with the bus suffix, sysfs-bus-mdio is
now a testing ABI, and didn't have Users in it. This is the time to change
it before it's moved to the stable ABI.
Change the bus name to mdio and update sysfs-bus-mdio.
Signed-off-by: Yajun Deng <yajun.deng@linux.dev>
---
v2: update sysfs-bus-mdio
v1: https://lore.kernel.org/all/20241219065855.1377069-1-yajun.deng@linux.dev/
---
Documentation/ABI/testing/sysfs-bus-mdio | 54 ++++++++++++------------
drivers/net/phy/mdio_bus.c | 2 +-
2 files changed, 28 insertions(+), 28 deletions(-)
diff --git a/Documentation/ABI/testing/sysfs-bus-mdio b/Documentation/ABI/testing/sysfs-bus-mdio
index 38be04dfc05e..a1fad1d0b8fa 100644
--- a/Documentation/ABI/testing/sysfs-bus-mdio
+++ b/Documentation/ABI/testing/sysfs-bus-mdio
@@ -1,72 +1,72 @@
-What: /sys/bus/mdio_bus/devices/.../statistics/
+What: /sys/bus/mdio/devices/.../statistics/
What: /sys/class/mdio_bus/.../statistics/
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
This folder contains statistics about global and per
MDIO bus address statistics.
-What: /sys/bus/mdio_bus/devices/.../statistics/transfers
+What: /sys/bus/mdio/devices/.../statistics/transfers
What: /sys/class/mdio_bus/.../transfers
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
Total number of transfers for this MDIO bus.
-What: /sys/bus/mdio_bus/devices/.../statistics/errors
+What: /sys/bus/mdio/devices/.../statistics/errors
What: /sys/class/mdio_bus/.../statistics/errors
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
Total number of transfer errors for this MDIO bus.
-What: /sys/bus/mdio_bus/devices/.../statistics/writes
+What: /sys/bus/mdio/devices/.../statistics/writes
What: /sys/class/mdio_bus/.../statistics/writes
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
Total number of write transactions for this MDIO bus.
-What: /sys/bus/mdio_bus/devices/.../statistics/reads
+What: /sys/bus/mdio/devices/.../statistics/reads
What: /sys/class/mdio_bus/.../statistics/reads
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
Total number of read transactions for this MDIO bus.
-What: /sys/bus/mdio_bus/devices/.../statistics/transfers_<addr>
+What: /sys/bus/mdio/devices/.../statistics/transfers_<addr>
What: /sys/class/mdio_bus/.../statistics/transfers_<addr>
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
Total number of transfers for this MDIO bus address.
-What: /sys/bus/mdio_bus/devices/.../statistics/errors_<addr>
+What: /sys/bus/mdio/devices/.../statistics/errors_<addr>
What: /sys/class/mdio_bus/.../statistics/errors_<addr>
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
Total number of transfer errors for this MDIO bus address.
-What: /sys/bus/mdio_bus/devices/.../statistics/writes_<addr>
+What: /sys/bus/mdio/devices/.../statistics/writes_<addr>
What: /sys/class/mdio_bus/.../statistics/writes_<addr>
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
Total number of write transactions for this MDIO bus address.
-What: /sys/bus/mdio_bus/devices/.../statistics/reads_<addr>
+What: /sys/bus/mdio/devices/.../statistics/reads_<addr>
What: /sys/class/mdio_bus/.../statistics/reads_<addr>
-Date: January 2020
-KernelVersion: 5.6
+Date: January 2025
+KernelVersion: 6.13
Contact: netdev@vger.kernel.org
Description:
Total number of read transactions for this MDIO bus address.
diff --git a/drivers/net/phy/mdio_bus.c b/drivers/net/phy/mdio_bus.c
index 7e2f10182c0c..20dd59208973 100644
--- a/drivers/net/phy/mdio_bus.c
+++ b/drivers/net/phy/mdio_bus.c
@@ -1425,7 +1425,7 @@ static const struct attribute_group *mdio_bus_dev_groups[] = {
};
const struct bus_type mdio_bus_type = {
- .name = "mdio_bus",
+ .name = "mdio",
.dev_groups = mdio_bus_dev_groups,
.match = mdio_bus_match,
.uevent = mdio_uevent,
--
2.25.1
next reply other threads:[~2024-12-19 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 10:04 Yajun Deng [this message]
2024-12-19 10:20 ` [PATCH net-next v2] net: mdio_bus: change the bus name to mdio Andrew Lunn
2024-12-19 16:52 ` Florian Fainelli
2024-12-20 1:34 ` Yajun Deng
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=20241219100454.1623211-1-yajun.deng@linux.dev \
--to=yajun.deng@linux.dev \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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).