netdev - Re: [PATCH net-next v2 01/10] net: dsa: lan9303: Fixed MDIO interface

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]

Date:   Wed, 26 Jul 2017 22:47:22 +0200
From:   Egil Hjelmeland <privat@...l-hjelmeland.no>
To:     David Miller <davem@...emloft.net>, andrew@...n.ch
Cc:     vivien.didelot@...oirfairelinux.com, corbet@....net,
        f.fainelli@...il.com, kernel@...gutronix.de,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 01/10] net: dsa: lan9303: Fixed MDIO interface

Den 26. juli 2017 22:07, skrev David Miller:
> From: Andrew Lunn <andrew@...n.ch>
> Date: Wed, 26 Jul 2017 19:52:24 +0200
> 
>>>> So I really want to group the patches into only a few series in order
>>>> to not spend months on the process.
>>
>> I strongly agree with Vivien here. Good patches get accepted in about
>> 3 days. You should expect feedback within a day or two. That allows
>> you to have fast cycle times for getting patches in.
> 
> +1
> 
> Small simple patches will get everything in 10 times fast than if
> you clump everything together into larger, harder to review ones.
> 

Good. Just one question about process. Could I have posted my work
as a RFC? To get one round of initial feedback before chopping into
small patch requests. As well as indicating where I am heading. Or is
that just waste of human bandwidth?

Egil