Re: NET: r8168/r8169 identifying fix

[Heiner Kallweit <hkallweit1@gmail.com>]

On 15.04.2020 16:39, Lauri Jakku wrote:
> Hi,
> 
> There seems to he Something odd problem, maybe timing related. Stripped version not workingas expected. I get back to you, when  i have it working.

There's no point in working on your patch. W/o proper justification it
isn't acceptable anyway. And so far we still don't know which problem
you actually have.
FIRST please provide the requested logs and explain the actual problem
(incl. the commit that caused the regression).


> 13. huhtik. 2020, 14.46, Lauri Jakku <ljakku77@gmail.com <mailto:ljakku77@gmail.com>> kirjoitti:
> 
>     Hi,
> 
>     Fair enough, i'll strip them.
> 
>     -lja
> 
>     On 2020-04-13 14:34, Leon Romanovsky wrote:
> 
>         On Mon, Apr 13, 2020 at 02:02:01PM +0300, Lauri Jakku wrote:
> 
>             Hi,
> 
>             Comments inline.
> 
>             On 2020-04-13 13:58, Leon Romanovsky wrote:
> 
>                 On Mon, Apr 13, 2020 at 01:30:13PM +0300, Lauri Jakku wrote:
> 
>                     From 2d41edd4e6455187094f3a13d58c46eeee35aa31 Mon Sep 17 00:00:00 2001
>                     From: Lauri Jakku <lja@iki.fi>
>                     Date: Mon, 13 Apr 2020 13:18:35 +0300
>                     Subject: [PATCH] NET: r8168/r8169 identifying fix
> 
>                     The driver installation determination made properly by
>                     checking PHY vs DRIVER id's.
>                     ---
>                     drivers/net/ethernet/realtek/r8169_main.c | 70 ++++++++++++++++++++---
>                     drivers/net/phy/mdio_bus.c | 11 +++-
>                     2 files changed, 72 insertions(+), 9 deletions(-)
> 
> 
>                 I would say that most of the code is debug prints.
> 
> 
> 
>             I tought that they are helpful to keep, they are using the debug calls, so
>             they are not visible if user does not like those.
> 
> 
>         You are missing the point of who are your users.
> 
>         Users want to have working device and the code. They don't need or like
>         to debug their kernel.
> 
>         Thanks
>