From: Andrew Lunn <andrew@lunn.ch>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, dlan@kernel.org,
edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
netdev@vger.kernel.org, pabeni@redhat.com,
spacemit@lists.linux.dev, wangruikang@iscas.ac.cn
Subject: Re: [PATCH 1/1] net: spacemit: display phy driver information
Date: Thu, 22 Jan 2026 16:18:25 +0100 [thread overview]
Message-ID: <4493e09c-e4fb-424d-a44a-1e4d4510e4e2@lunn.ch> (raw)
In-Reply-To: <20260122150601.586846-1-amadeus@jmu.edu.cn>
On Thu, Jan 22, 2026 at 11:06:01PM +0800, Chukun Pan wrote:
> Hi,
>
> > > Print the PHY driver used and interrupt status after connection.
> >
> > The standard way to do this is call phy_attached_info(). Is it missing
> > some information you need?
>
> I initially used phy_attached_info(), but it was too long and printed
> phydev_name() "cac80000.ethernet:01" twice:
>
> YT8531 Gigabit Ethernet cac80000.ethernet:01: attached PHY driver (mii_bus:phy_addr=cac80000.ethernet:01, irq=POLL)
This is what everybody expects, so you should use it.
You have some control over the names, it is the name you assign when
creating the struct device. Maybe you can shorten them.
Andrew
next prev parent reply other threads:[~2026-01-22 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 8:00 [PATCH 1/1] net: spacemit: display phy driver information Chukun Pan
2026-01-22 13:17 ` Andrew Lunn
2026-01-22 15:06 ` Chukun Pan
2026-01-22 15:18 ` Andrew Lunn [this message]
2026-01-23 2:10 ` Vivian Wang
2026-01-22 15:12 ` Yao Zi
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=4493e09c-e4fb-424d-a44a-1e4d4510e4e2@lunn.ch \
--to=andrew@lunn.ch \
--cc=amadeus@jmu.edu.cn \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dlan@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=spacemit@lists.linux.dev \
--cc=wangruikang@iscas.ac.cn \
/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