Re: [patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Fri Jan 21 2000 - 21:46:37 EST

Next message: Piete Brooks: "Re: Changes in fork ?"
Previous message: H. Peter Anvin: "Re: Constant byteorder macros."
In reply to: Jes Sorensen: "Re: [patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)"
Next in thread: Matthew Wilcox: "Re: [patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)"
Reply: Matthew Wilcox: "Re: [patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Wrong again, it makes the code less readable because kzalloc() is a
> non standard function name. This looks more to me like a patch just
> for the sake of the patch.

Since when has "kmalloc" been a standard name anyway ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Piete Brooks: "Re: Changes in fork ?"
Previous message: H. Peter Anvin: "Re: Constant byteorder macros."
In reply to: Jes Sorensen: "Re: [patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)"
Next in thread: Matthew Wilcox: "Re: [patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)"
Reply: Matthew Wilcox: "Re: [patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:27 EST