| 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
| ||
|
Message-Id: <20130614.140422.262779440905577037.davem@davemloft.net> Date: Fri, 14 Jun 2013 14:04:22 -0700 (PDT) From: David Miller <davem@...emloft.net> To: jesse@...ira.com Cc: pshelar@...ira.com, netdev@...r.kernel.org, dev@...nvswitch.org Subject: Re: [PATCH net-next v2 0/4] openvswitch tunneling preparation From: Jesse Gross <jesse@...ira.com> Date: Fri, 14 Jun 2013 08:28:41 -0700 > On Thu, Jun 13, 2013 at 5:05 PM, David Miller <davem@...emloft.net> wrote: >> From: Pravin B Shelar <pshelar@...ira.com> >> Date: Thu, 13 Jun 2013 11:11:19 -0700 >> >>> Following patches are required but not directly related to ovs tunneling. >>> So I am sending them as separate series. These cleanups are already >>> there in out of tree ovs module. >>> >>> Since ovs tunneling series depends on this, I am sending all patches >>> again. >> >> Openvswitch folks please send me a pull request. > > For the non-OVS portions of the tunneling series (not this one, which > I already applied, but the next) do you want to take them directly or > should I just throw them all into my tree? I was hoping you would send me a pull request for the initial 4 patch series et al. Then get your ACK's for the openvswitch parts of the big tunneling patch set so that I could just apply the entire thing myself. -- 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