All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	linux-kernel@vger.kernel.org, jirislaby@gmail.com,
	lion.vollnhals@web.de
Subject: Re: [PATCH] use kzalloc instead of malloc+memset
Date: Tue, 13 Sep 2005 19:31:53 +0300	[thread overview]
Message-ID: <1126629113.8494.0.camel@localhost> (raw)
In-Reply-To: <17190.33539.992902.463545@gargle.gargle.HOWL>

Pekka J Enberg writes:
>  > +The kernel provides the following general purpose memory allocators:
>  > +kmalloc(), kzalloc(), kcalloc(), and vmalloc().  Please refer to the API
>  > +documentation for further information about them.
>  > +
>  > +The preferred form for passing a size of a struct is the following:
>  > +
>  > +	p = kmalloc(sizeof(*p), ...);

On Tue, 2005-09-13 at 11:42 +0400, Nikita Danilov wrote:
> Parentheses around *p are superfluous. See

Sure but is it the preferred form for the kernel?

			Pekka


  reply	other threads:[~2005-09-13 16:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 22:10 [PATCH] use kzalloc instead of malloc+memset Lion Vollnhals
2005-09-12 22:47 ` Lion Vollnhals
2005-09-13  5:41   ` Denis Vlasenko
2005-09-13 11:27     ` Jiri Slaby
2005-09-12 22:58 ` Jiri Slaby
2005-09-13  4:43   ` Pekka Enberg
2005-09-13  5:33     ` Dmitry Torokhov
2005-09-13  6:42       ` Andrew Morton
2005-09-13  7:02         ` Pekka J Enberg
2005-09-13  7:42           ` Nikita Danilov
2005-09-13 16:31             ` Pekka Enberg [this message]
2005-09-14  5:02             ` Denis Vlasenko
2005-09-14  9:58               ` Nikita Danilov
2005-09-13 23:28         ` Paul Jackson
2005-09-14  9:33           ` Bernd Petrovitsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1126629113.8494.0.camel@localhost \
    --to=penberg@cs.helsinki.fi \
    --cc=dtor_core@ameritech.net \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lion.vollnhals@web.de \
    --cc=nikita@clusterfs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.