Re: [ovs-dev] [PATCH] Limit the split elements to 2 (maxsplit + 1)

2015-03-03 Thread Gurucharan Shetty
On Mon, Mar 2, 2015 at 1:41 PM, Mark Maglana wrote: > This change ensures that we always end up with two elements even > if the name of the physical port contains dashes. For example, a > binding of "0100-br0-eth1" will be split to ["0100", "br0-eth1"] > instead of ["0100", "br0", "eth1"]. > > Sig

Re: [ovs-dev] [PATCH] Limit the split elements to 2 (maxsplit + 1)

2015-03-02 Thread Ben Pfaff
On Mon, Mar 02, 2015 at 01:41:35PM -0800, Mark Maglana wrote: > This change ensures that we always end up with two elements even > if the name of the physical port contains dashes. For example, a > binding of "0100-br0-eth1" will be split to ["0100", "br0-eth1"] > instead of ["0100", "br0", "eth1"]

[ovs-dev] [PATCH] Limit the split elements to 2 (maxsplit + 1)

2015-03-02 Thread Mark Maglana
This change ensures that we always end up with two elements even if the name of the physical port contains dashes. For example, a binding of "0100-br0-eth1" will be split to ["0100", "br0-eth1"] instead of ["0100", "br0", "eth1"]. Signed-off-by: Mark Maglana --- vtep/ovs-vtep | 2 +- 1 file chan