| 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
| ||
|
Date: Tue, 9 Dec 2014 10:36:14 -0800 From: Pravin Shelar <pshelar@...ira.com> To: Lori Jakab <lojakab@...co.com> Cc: netdev <netdev@...r.kernel.org>, "dev@...nvswitch.org" <dev@...nvswitch.org> Subject: Re: [ovs-dev] OVS Kernel Datapath development On Tue, Dec 9, 2014 at 10:02 AM, Lori Jakab <lojakab@...co.com> wrote: > On 12/08/2014 06:47 AM, Pravin Shelar wrote: >> Since the beginning OVS kernel datapath development is primarily done >> on external OVS repo. Now we have mostly synced upstream and external >> OVS. So we have decided to change this process. New process is as >> follows. > > Patch series that have previous revisions already reviewed with the old > process should now switch to the new process? Or does the change apply > only to new patch series? > All patch series should follow new process including the one which got reviewed partially. > -Lori > >> >> 1. OVS feature development that involves kernel datapath should be >> done on net-next tree datapath. >> 2. Such feature patch series should be posted on netdev and ovs-dev >> mailing list. >> 3. Once review is done for entire series, kernel and OVS userspace >> patches will be merged in respective repo. >> 4. After the merge developer is suppose to send patches for external >> kernel datapath along with old kernel compatibility code. So that we >> can keep external datapath insync. >> >> >> Thanks, >> Pravin. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists