Re: [PATCH 1/1] net: dw_eth_qos: Add missing \n in error messages.

2024-04-10 Thread Tom Rini
On Tue, 02 Apr 2024 10:39:34 +0200, Heinrich Schuchardt wrote: > Missing line-feeds in error messages lead to output like: > > phy_startup() failed: -110FAILED: -110=> > > Output like the following is much easier to read: > > phy_startup() failed: -110 > FAILED: -110 > => > >

Re: [PATCH 1/1] net: dw_eth_qos: Add missing \n in error messages.

2024-04-02 Thread Heinrich Schuchardt
On 02.04.24 13:26, Quentin Schulz wrote: Hi Heinrich, On 4/2/24 10:39, Heinrich Schuchardt wrote: Missing line-feeds in error messages lead to output like: phy_startup() failed: -110FAILED: -110=> Output like the following is much easier to read: phy_startup() failed: -110

Re: [PATCH 1/1] net: dw_eth_qos: Add missing \n in error messages.

2024-04-02 Thread Quentin Schulz
Hi Heinrich, On 4/2/24 10:39, Heinrich Schuchardt wrote: Missing line-feeds in error messages lead to output like: phy_startup() failed: -110FAILED: -110=> Output like the following is much easier to read: phy_startup() failed: -110 FAILED: -110 => Signed-off-by:

[PATCH 1/1] net: dw_eth_qos: Add missing \n in error messages.

2024-04-02 Thread Heinrich Schuchardt
Missing line-feeds in error messages lead to output like: phy_startup() failed: -110FAILED: -110=> Output like the following is much easier to read: phy_startup() failed: -110 FAILED: -110 => Signed-off-by: Heinrich Schuchardt --- drivers/net/dwc_eth_qos.c | 108