Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+nf\-next\s+9\/9\]\s+ipvs\:\s+Use\s+network\s+byte\s+order\s+for\s+sync\s+message\s+size\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+nf\-next\s+9\/9\]\s+ipvs\:\s+Use\s+network\s+byte\s+order\s+for\s+sync\s+message\s+size\s*$/: 1 ]

Total 1 documents matching your query.

1. [PATCH nf-next 9/9] ipvs: Use network byte order for sync message size (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Tue, 23 Apr 2013 12:04:00 +0900; struct ip_vs_sync_mesg and ip_vs_sync_mesg_v0 are both sent across the wire and used internally to store IPVS synchronisation messages. Up until now the scheme used has been to convert the size field; /html/lvs-devel/2013-04/msg00051.html (15,033 bytes)

Current List: 1 - 1
Page: [1]