Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\s+5\/6\]\s+ipvs\:\s+fix\s+sparse\s+warnings\s+for\s+some\s+parameters\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [PATCH net-next 5/6] ipvs: fix sparse warnings for some parameters (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Fri, 19 Apr 2013 08:59:44 +0900
Thanks, I understand. That is rather unfortunate but as you say we are somewhat stuck. I have queued-up this patch in ipvs-next. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel
/html/lvs-devel/2013-04/msg00031.html (24,915 bytes)

2. Re: [PATCH net-next 5/6] ipvs: fix sparse warnings for some parameters (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Thu, 18 Apr 2013 23:00:55 +0300 (EEST)
Hello, These occurances are only in this diff to access the prefix len, there are other places that use the big-endian value. The problem comes with the IPVS-IPv6 support: in same attribute we provid
/html/lvs-devel/2013-04/msg00028.html (23,377 bytes)

3. Re: [PATCH net-next 5/6] ipvs: fix sparse warnings for some parameters (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Thu, 18 Apr 2013 20:53:56 +0900
Its not clear to me that netmask should be __be32 given the occurrences of (__force __u32) below. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to m
/html/lvs-devel/2013-04/msg00023.html (22,317 bytes)

4. [PATCH net-next 5/6] ipvs: fix sparse warnings for some parameters (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 17 Apr 2013 23:50:49 +0300
Some service fields are in network order: - netmask: used once in network order and also as prefix len for IPv6 - port Other parameters are in host order: - struct ip_vs_flags: flags and mask moved b
/html/lvs-devel/2013-04/msg00012.html (18,413 bytes)


This search system is powered by Namazu