netdev - Re: [PATCH net-next v2 0/9] Add support for OPEN Alliance 10BASE-T1x MACPHY Serial 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]

Message-ID: <e819bb00-f046-4f19-af83-2529f2141fa6@lunn.ch>
Date: Mon, 19 Feb 2024 15:30:55 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Parthiban.Veerasooran@...rochip.com
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
	pabeni@...hat.com, Steen.Hegelund@...rochip.com,
	netdev@...r.kernel.org, Horatiu.Vultur@...rochip.com,
	Woojung.Huh@...rochip.com, Nicolas.Ferre@...rochip.com,
	UNGLinuxDriver@...rochip.com, Thorsten.Kummermehr@...rochip.com,
	Pier.Beruto@...emi.com, Selvamani.Rajagopal@...emi.com
Subject: Re: [PATCH net-next v2 0/9] Add support for OPEN Alliance 10BASE-T1x
 MACPHY Serial Interface

> Hi Andrew,
> 
>  From Microchip side, we haven't stopped/postponed this framework 
> development. We are already working on it. It is in the final stage now. 
> We are doing internal reviews right now and we expect that in 3 weeks 
> time frame in the mainline again. We will send a new version (v3) of 
> this patch series soon.

Hi Parthiban

It is good to here you are still working on it.

A have a few comments about how Linux mainline works. It tends to be
very iterative. Cycles tend to be fast. You will probably get review
comments within a couple of days of posting code. You often see
developers posting a new version within a few days, maybe a week. If
reviewers have asked for large changes, it can take longer, but
general, the cycles are short.

When you say you need three weeks for internal review, that to me
seems very slow. Is it so hard to get access to internal reviewers? Do
you have a very formal review process? More waterfall than iterative
development? I would suggest you try to keep your internal reviews
fast and low overhead, because you will be doing it lots of times as
we iterate the framework.

	Andrew