Re: [ovs-dev] [PATCH 1/2] rhel: Prioritize our vport-foo modules in depmod.

Thanks for the reviews all, I pushed this to master. On 29 July 2016 at 11:46, Flavio Leitner wrote: > On Thu, Jul 28, 2016 at 05:09:37PM -0700, Joe Stringer wrote: >> We've done the same for openvswitch.ko previously, but we really should >> be doing this for vport modules as

Re: [ovs-dev] [PATCH 1/2] rhel: Prioritize our vport-foo modules in depmod.

On 29 July 2016 at 11:38, pravin shelar wrote: > On Thu, Jul 28, 2016 at 5:09 PM, Joe Stringer wrote: >> We've done the same for openvswitch.ko previously, but we really should >> be doing this for vport modules as well; otherwise, depmod may try to >> pair

Re: [ovs-dev] [PATCH 1/2] rhel: Prioritize our vport-foo modules in depmod.

On Thu, Jul 28, 2016 at 05:09:37PM -0700, Joe Stringer wrote: > We've done the same for openvswitch.ko previously, but we really should > be doing this for vport modules as well; otherwise, depmod may try to > pair upstream vport modules with the out-of-tree openvswitch module > (leading to depmod

Re: [ovs-dev] [PATCH 1/2] rhel: Prioritize our vport-foo modules in depmod.

On Thu, Jul 28, 2016 at 5:09 PM, Joe Stringer wrote: > We've done the same for openvswitch.ko previously, but we really should > be doing this for vport modules as well; otherwise, depmod may try to > pair upstream vport modules with the out-of-tree openvswitch module > (leading to

[ovs-dev] [PATCH 1/2] rhel: Prioritize our vport-foo modules in depmod.

We've done the same for openvswitch.ko previously, but we really should be doing this for vport modules as well; otherwise, depmod may try to pair upstream vport modules with the out-of-tree openvswitch module (leading to depmod warnings on package install, and failure to load the module at