From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
f.fainelli@gmail.com, vivien.didelot@gmail.com
Subject: Re: [PATCH net] net: dsa: change PHY error message again
Date: Mon, 24 Aug 2020 00:26:43 +0200 [thread overview]
Message-ID: <20200823222643.GL2588906@lunn.ch> (raw)
In-Reply-To: <20200823213520.2445615-1-olteanv@gmail.com>
On Mon, Aug 24, 2020 at 12:35:20AM +0300, Vladimir Oltean wrote:
> slave_dev->name is only populated at this stage if it was specified
> through a label in the device tree. However that is not mandatory.
Hi Vladimir
It is not mandatory, but it is normal.
> When it isn't, the error message looks like this:
>
> [ 5.037057] fsl_enetc 0000:00:00.2 eth2: error -19 setting up slave PHY for eth%d
> [ 5.044672] fsl_enetc 0000:00:00.2 eth2: error -19 setting up slave PHY for eth%d
> [ 5.052275] fsl_enetc 0000:00:00.2 eth2: error -19 setting up slave PHY for eth%d
> [ 5.059877] fsl_enetc 0000:00:00.2 eth2: error -19 setting up slave PHY for eth%d
>
> which is especially confusing since the error gets printed on behalf of
> the DSA master (fsl_enetc in this case).
>
> Printing an error message that contains a valid reference to the DSA
> port's name is difficult at this point in the initialization stage, so
> at least we should print some info that is more reliable, even if less
> user-friendly. That may be the driver name and the hardware port index.
>
> After this change, the error is printed as:
>
> [ 4.957403] mscc_felix 0000:00:00.5: error -19 setting up PHY for port 0
> [ 4.964231] mscc_felix 0000:00:00.5: error -19 setting up PHY for port 1
> [ 4.971055] mscc_felix 0000:00:00.5: error -19 setting up PHY for port 2
> [ 4.977871] mscc_felix 0000:00:00.5: error -19 setting up PHY for port 3
I would prefer both the port number and the interface name. With
setups using D in DSA, there are examples where port 1 on the first
switch is lan1, and port 1 of the second switch is lan5. Having both
avoids some confusion.
Another option would be to call dev_alloc_name() after
alloc_netdev_mqs() if there is no label. The eth%d will then get
replaced with a unique name.
> Fixes: 65951a9eb65e ("net: dsa: Improve subordinate PHY error message")
I'm not sure this actually meets the stable criteria.
Andrew
next prev parent reply other threads:[~2020-08-23 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 21:35 [PATCH net] net: dsa: change PHY error message again Vladimir Oltean
2020-08-23 22:26 ` Andrew Lunn [this message]
2020-08-24 3:37 ` Florian Fainelli
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=20200823222643.GL2588906@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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).