Thanks Simon, feel free to exercise this path anytime. Applied to nf, thanks! -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxx
Thanks Pablo, please do. Signed-off-by: Simon Horman <horms@xxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx
@Simon: If you have no more pending updates, I can save you one pull request for this small fix by placing this. Thanks! -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the
David -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Correct. I would hope that a sane version of gcc would just not perform the first write. What happens instead is that the version that produces the warning here moves the initialization to the top of
Hello, OK, Acked-by: Julian Anastasov <ja@xxxxxx> I guess, Simon will take the patch for ipvs-next. So, now there is a double write here? What about such constructs?: *ho = (struct ip_vs_seq) { .init
Building the ip_vs_sync code with CONFIG_OPTIMIZE_INLINING on x86 confuses the compiler to the point where it produces a rather dubious warning message: net/netfilter/ipvs/ip_vs_sync.c:1073:33: error