> Stick to one method that works for all routines, dynamic registration. > If that imposes the occasional need for a couple of extra calls in some > routines and for people to think about initialisation order right from > the start then so be it, it is a small price to pay for long term > stability and ease of maintenance. What happens when we get a loop in init order because of binding and other init order conflicts? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Where did vm_operations_struct->unmap in 2.4.0 go? Allen Unueco
- Re: Where did vm_operations_struct->unmap in 2.4.0... Keith Owens
- Re: Where did vm_operations_struct->unmap in 2.4.0... Antony Suter
- Re: Where did vm_operations_struct->unmap in 2... Keith Owens
- Re: Where did vm_operations_struct->unmap ... David Woodhouse
- Re: Where did vm_operations_struct->un... Keith Owens
- Re: Where did vm_operations_struct-&... David Woodhouse
- Re: Where did vm_operations_stru... Keith Owens
- Re: Where did vm_operations_... Alan Cox
- Re: Where did vm_operations_... Keith Owens
- Re: Where did vm_operations_... Ingo Oeser
- Re: Where did vm_operations_... Keith Owens
- Re: Where did vm_operations_... David Woodhouse
- Re: Where did vm_operations_... Keith Owens
- Re: Where did vm_operations_... David Woodhouse
- Re: Where did vm_operations_... Daniel Phillips
- Re: Where did vm_operations_... Keith Owens
- Re: Where did vm_operations_... Kai Henningsen
- Re: Where did vm_operations_... David Woodhouse