linux-kernel - Re: [PATCH net-next v4 3/7] net: axienet: Use MDIO bus device in prints

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6349fbbb-de1f-4ec9-abb0-96b4e2d37c97@linux.dev>
Date: Tue, 5 Aug 2025 17:15:59 -0400
From: Sean Anderson <sean.anderson@...ux.dev>
To: Andrew Lunn <andrew@...n.ch>
Cc: Radhey Shyam Pandey <radhey.shyam.pandey@....com>,
 Andrew Lunn <andrew+netdev@...n.ch>, "David S . Miller"
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, Greg Kroah-Hartman
 <gregkh@...uxfoundation.org>, Michal Simek <michal.simek@....com>,
 Leon Romanovsky <leon@...nel.org>
Subject: Re: [PATCH net-next v4 3/7] net: axienet: Use MDIO bus device in
 prints

On 8/5/25 17:07, Andrew Lunn wrote:
> On Tue, Aug 05, 2025 at 11:34:52AM -0400, Sean Anderson wrote:
>> For clarity and to remove the dependency on the parent netdev, use the
>> MDIO bus device in print statements.
> 
>> @@ -186,28 +187,31 @@ static int axienet_mdio_enable(struct axienet_local *lp, struct device_node *np)
>>  		/* Legacy fallback: detect CPU clock frequency and use as AXI
>>  		 * bus clock frequency. This only works on certain platforms.
>>  		 */
>> -		np1 = of_find_node_by_name(NULL, "cpu");
>> +		np1 = of_find_node_by_name(NULL, "lpu");
> 
> There is nothing about dev in this change?

Whoops, this was left over from doing s/lp/cp/ and then reverting
it when I decided that there would be too much diffstat. Will fix for v5.

--Sean