Yes, that is also shared between um-km. Thanks! Saurabh
From: Samuel Ghinet <sghi...@cloudbasesolutions.com<mailto:sghi...@cloudbasesolutions.com>> Date: Thursday, August 14, 2014 at 5:10 AM To: Saurabh Shah <ssaur...@vmware.com<mailto:ssaur...@vmware.com>>, Nithin Raju <nit...@vmware.com<mailto:nit...@vmware.com>>, Ankur Sharma <ankursha...@vmware.com<mailto:ankursha...@vmware.com>> Cc: "dev@openvswitch.org<mailto:dev@openvswitch.org>" <dev@openvswitch.org<mailto:dev@openvswitch.org>> Subject: RE: [ovs-dev] datapath-windows: Renaming files proposal If I leave OvsPub.h and OvsDpInterface.h intact, should I also leave OvsNetlink.h intact? Sam ________________________________________ From: Saurabh Shah [ssaur...@vmware.com<mailto:ssaur...@vmware.com>] Sent: Thursday, August 14, 2014 3:43 AM To: Samuel Ghinet; Nithin Raju; Ankur Sharma Cc: dev@openvswitch.org<mailto:dev@openvswitch.org> Subject: Re: [ovs-dev] datapath-windows: Renaming files proposal Hi Samuel, OvsNetlink.h -> Netlink.h OvsPub.h -> Pub.h The following will be left intact: OvsDpInterface.h Because it is a userspace interaction file and it is a generated file. I think I tried to tell this earlier, so this will be a repeat. If you want to nuke ŒOvs¹ please remove it from OvsDpInterface.h as well. If you want to keep the semantic that the userspace files should have an Ovs prefix, you should also keep the prefix for OvsPub.h. ‹ Saurabh _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
