There has been some misunderstanding on what an RFC patch is and what standards it needs to meet. Following is the official response of David Miller.
Based on those guidelines the RFC patch we submitted meets and exceeds the requirements. So please review it.
Replacement of function pointers will be addressed later as a separate issue.
In case there are other procedural issues that would prohibit technical discussion please site the written rules or first ask David Miller.
There are a lot of technical issues to discuss, so if possible lets not get tied up on process and bureaucracy. Looking forward to detailed technical comments.
-------- Forwarded Message --------
Subject: Re: Few questions about submitting patches Date: Wed, 21 Mar 2018 12:46:17 -0400 (EDT) From: David Miller <davem@davemloft.net> To: rao.shoaib@oracle.com CC: netdev@vger.kernel.org, eric.dumazet@gmail.com > * #ifdef FOO > > In a regular patch consisting of a series of patches, can the above > #ifdef be used in a patch before the patch that allows the selection > of FOO. That patch is part of the series but comes later. It is better to introduce them at the same time. But if it is prohibitively difficult to do so, yet at the same time properly split up your changes into manageable pieces, it can be OK. It is definitely determined on a case by case basis.
![]() | Matthieu Baerts | R&D Engineer |
matthieu.baerts@tessares.net | |
Tessares SA | Hybrid Access Solutions www.tessares.net 1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium |