Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\s+2\/6\]\s+ipvs\:\s+fix\s+sparse\s+warnings\s+for\s+ip_vs

Results:

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

Total 2 documents matching your query.

1. Re: [PATCH net-next 2/6] ipvs: fix sparse warnings for ip_vs_conn listing (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Thu, 18 Apr 2013 20:46:58 +0900; Thanks, this seems correct to me. I have queued it up in ipvs-next. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More; /html/lvs-devel/2013-04/msg00022.html (15,037 bytes)
2. [PATCH net-next 2/6] ipvs: fix sparse warnings for ip_vs_conn listing (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Wed, 17 Apr 2013 23:50:46 +0300; kbuild test robot reports for sparse warnings in commit 088339a57d6042 ("ipvs: convert connection locking"): net/netfilter/ipvs/ip_vs_conn.c:962:13: warning: context imbalance in 'ip_vs_conn_array' -; /html/lvs-devel/2013-04/msg00013.html (12,837 bytes)

Current List: 1 - 2
Page: [1]