Re: [IPSEC] Move dst->child loop from dst_ifdown to xfrm_dst_ifdown

2005-02-15 Thread David S. Miller
On Tue, 8 Feb 2005 12:31:40 +1100 Herbert Xu <[EMAIL PROTECTED]> wrote: > On Tue, Feb 08, 2005 at 12:29:29PM +1100, herbert wrote: > > > > This one moves the dst->child processing from dst_ifdown into > > xfrm_dst_ifdown. > > This patch adds a net_device argument to ifdown. After all, > it's a

Re: [IPSEC] Move dst->child loop from dst_ifdown to xfrm_dst_ifdown

2005-02-07 Thread Herbert Xu
On Tue, Feb 08, 2005 at 12:29:29PM +1100, herbert wrote: > > This one moves the dst->child processing from dst_ifdown into > xfrm_dst_ifdown. This patch adds a net_device argument to ifdown. After all, it's a bit silly to notify someone of an ifdown event without telling them what which device i

[IPSEC] Move dst->child loop from dst_ifdown to xfrm_dst_ifdown

2005-02-07 Thread Herbert Xu
On Sun, Feb 06, 2005 at 05:51:17PM +1100, herbert wrote: > > The idea is to move the check into dst->ops->ifdown. By definition > ipv6_dst_ifdown will only see rt6_info entries. So dst_dev_event > will become Here are the patches to do this. Do they look sane? This one moves the dst->child pr