Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nf\-next\s+PATCH\s+v2\]\s+ipvs\:\s+fix\s+build\s+errors\s+related\s+to\s+config\s+option\s+combinations\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nf\-next\s+PATCH\s+v2\]\s+ipvs\:\s+fix\s+build\s+errors\s+related\s+to\s+config\s+option\s+combinations\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [nf-next PATCH v2] ipvs: fix build errors related to config option combinations (score: 1): Author: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx>; Date: Tue, 23 Oct 2012 10:53:20 +0200; By looking at all those CONFIG_IP_VS_IPV6. I'd suggest to abstract generic layer 3 operations and thus move all IPv4 and IPv6 to the corresponding files (eg. ipvs_l3proto_ipv4.c and ipvs_l3proto_ipv6; /html/lvs-devel/2012-10/msg00019.html (12,042 bytes)
2. Re: [nf-next PATCH v2] ipvs: fix build errors related to config option combinations (score: 1): Author: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx>; Date: Tue, 23 Oct 2012 10:42:41 +0200; David already mentioned that we (Netfilter/IPVS) should aim to reduce the amount of ifdef pollution in the code. Sometimes it is possible in a nice way by encapsulating code that depends on the featu; /html/lvs-devel/2012-10/msg00017.html (11,755 bytes)
3. Re: [nf-next PATCH v2] ipvs: fix build errors related to config option combinations (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Tue, 23 Oct 2012 09:33:15 +0900; Thanks, I have verified both of these fixes and I will send a pull request ASAP. I do wonder how we might get earlier test coverage of these kinds of problems. -- To unsubscribe from this list: send; /html/lvs-devel/2012-10/msg00014.html (12,280 bytes)
4. [nf-next PATCH v2] ipvs: fix build errors related to config option combinations (score: 1): Author: Jesper Dangaard Brouer <brouer@xxxxxxxxxx>; Date: Mon, 22 Oct 2012 21:22:45 +0200; Fix two build error introduced by commit 63dca2c0: "ipvs: Fix faulty IPv6 extension header handling in IPVS" First build error was fairly trivial and can occur, when CONFIG_IP_VS_IPV6 is disabled. Th; /html/lvs-devel/2012-10/msg00012.html (11,154 bytes)

Current List: 1 - 4
Page: [1]