netdev - Re: [PATCH net-next] net: phy: Add support for asking the PHY its abilities

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: <addc4332-bf56-dd86-d70f-5001db5192b0@gmail.com>
Date:   Sat, 9 Feb 2019 20:50:36 +0100
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     Andrew Lunn <andrew@...n.ch>,
        Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc:     Florian Fainelli <f.fainelli@...il.com>,
        David Miller <davem@...emloft.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] net: phy: Add support for asking the PHY its
 abilities

On 09.02.2019 20:42, Andrew Lunn wrote:
>> I know, it's patch 15 in your series ;) And I'm aware that usually new
>> core functionality is acceptable only if it comes together with a user,
>> to avoid having billions of orphaned good ideas in the code.
>> I focused on the core here to not get lost in all the new stuff, and to
>> provide Maxime with some direction for adjusting his series.
> 
> I'm just trying to avoid Maxime reimplementing something when we
> already have a patch:
> 
Sure, I didn't mean Maxime should re-implement things we have in the pipe.
I meant it more in a way that he gets an idea in which direction we're moving.

> https://github.com/lunn/linux/commit/07e3fa8f183f05a09d969a9378534da35238eeb9
> 
> Maxime, feel free to cherry-pick this into your series.
> 
I'll submit this one too.

> 	Andrew
> 
Heiner

Oh, and I just saw: When we talk about/with somebody, we should add him to the
mail addressee list.