Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+nf\-next\]\s+ipvs\:\s+use\s+nf_ct

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+nf\-next\]\s+ipvs\:\s+use\s+nf_ct_kill\s+helper\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [PATCH nf-next] ipvs: use nf_ct_kill helper (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Wed, 3 Aug 2016 10:37:21 +0300 (EEST); Hello, May be it would be better to preserve the debug messages, i.e. if we replace del_timer with nf_ct_kill and remove the ct->timeout.function call below. I assume nf_ct_kill still returns such bo; /html/lvs-devel/2016-08/msg00005.html (10,848 bytes)
2. [PATCH nf-next] ipvs: use nf_ct_kill helper (score: 1): Author: Florian Westphal <fw@xxxxxxxxx>; Date: Wed, 3 Aug 2016 02:51:05 +0200; Once timer is removed from nf_conn struct we cannot open-code the removal sequence like this anymore. Signed-off-by: Florian Westphal <fw@xxxxxxxxx> -- ipvs maintainers: Alternatively I can do a 1:1; /html/lvs-devel/2016-08/msg00004.html (9,840 bytes)

Current List: 1 - 2
Page: [1]