Search String: Display: Description: Sort:

Results:

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

Total 9 documents matching your query.

1. Re: [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Tue, 23 Apr 2013 11:52:32 +0900
[snip] [snip] Thanks, I have added your Acks and queued-up this this change in ipvs-next. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo
/html/lvs-devel/2013-04/msg00047.html (18,099 bytes)

2. Re: [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Hans Schillstrom <hans@xxxxxxxxxxxxxxx>
Date: Mon, 22 Apr 2013 07:55:51 +0200
Hello Simon It looks good Ack-by: Hans Schillstrom <hans@xxxxxxxxxxxxxxx> Attachment: smime.p7s Description: S/MIME cryptographic signature
/html/lvs-devel/2013-04/msg00041.html (20,810 bytes)

3. Re: [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Mon, 22 Apr 2013 08:39:46 +0300 (EEST)
Hello, v2 looks good, Acked-by: Julian Anastasov <ja@xxxxxx> Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message t
/html/lvs-devel/2013-04/msg00040.html (18,675 bytes)

4. Re: [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Mon, 22 Apr 2013 13:05:21 +0900
Thanks and sorry for missing that. How about this? ipvs: Use network byte order for sync message size struct ip_vs_sync_mesg and ip_vs_sync_mesg_v0 are both sent across the wire and used internally t
/html/lvs-devel/2013-04/msg00037.html (19,220 bytes)

5. Re: [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Fri, 19 Apr 2013 22:35:04 +0300 (EEST)
Hello, It seems v0 should be changed too, ip_vs_send_sync_msg() handles both versions in sb->mesg. Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe
/html/lvs-devel/2013-04/msg00033.html (14,708 bytes)

6. Re: [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Fri, 19 Apr 2013 10:49:55 +0900
Sure, sorry for not explaining myself more clearly. My idea is as follows: ipvs: Use network byte order for sync message size struct ip_vs_sync_mesg is both sent across the wire and used internally t
/html/lvs-devel/2013-04/msg00032.html (17,123 bytes)

7. Re: [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Thu, 18 Apr 2013 22:24:58 +0300 (EEST)
Hello, AFAIK, __force is the only way to suppress sparse warning. Not sure what is your idea, may be you can try it. Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the
/html/lvs-devel/2013-04/msg00025.html (14,580 bytes)

8. Re: [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Thu, 18 Apr 2013 20:43:30 +0900
I'm not very excited by the use of __force. Can't we change the type of the size element of struct ip_vs_sync_mesg and use the sparse annotations to our advantage? -- To unsubscribe from this list: s
/html/lvs-devel/2013-04/msg00019.html (13,487 bytes)

9. [PATCH net-next 4/6] ipvs: fix sparse warnings for sync msg size (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 17 Apr 2013 23:50:48 +0300
Fix sparse warnings while changing the size between host and network order: net/netfilter/ipvs/ip_vs_sync.c:1179:20: warning: cast to restricted __be16 net/netfilter/ipvs/ip_vs_sync.c:1179:20: warnin
/html/lvs-devel/2013-04/msg00015.html (11,636 bytes)


This search system is powered by Namazu