Hello, Thanks! I guess this is related to formatting of output, you can submit it as official change, so that we can apply all pending changes to the ipvsadm tree. Regards -- Julian Anastasov <ja@xxx
Hey Julian, Hello Alex, So, if I understand correctly, we'll wait until it lands in net-next and then I'll submit these patches to netdev? I think, you can now submit the patchset, net was merged to
Hello Alex, I think, you can now submit the patchset, net was merged to net-next, so you need a fresh net-next copy. Also, can you try my ipvsadm patches to check for possible problems in the connect
I'd prefer if Alex reposted them when the time comes to apply them. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More
Hello, ok Yes, we'll wait the patch but then post them again here, so that Simon can apply them to ipvs-next. Simon then adds netdev to CC list. Simon can say if he agrees to keep them somewhere unti
Hey Hello, Use the new address family field cp->daf when printing Signed-off-by: Julian Anastasov <ja@xxxxxx> Signed-off-by: Alex Gartrell <agartrell@xxxxxx> ... -- a/net/netfilter/ipvs/ip_vs_conn.c
Hello, ... Thanks! Note that for v4 we use 8+1 (hex). All other patches look ok. It is early to ack them, right? We need to post them again at the right time. I hope "ipvs: properly declare tunnel en
Use the new address family field cp->daf when printing Signed-off-by: Julian Anastasov <ja@xxxxxx> Signed-off-by: Alex Gartrell <agartrell@xxxxxx> -- net/netfilter/ipvs/ip_vs_conn.c | 49 ++++++++++++