public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Panagiotis Issaris <takis@gna.org>
To: "Daniel K." <daniel@cluded.net>
Cc: Panagiotis Issaris <takis@lumumba.uhasselt.be>,
	linux-kernel@vger.kernel.org, len.brown@intel.com,
	chas@cmf.nrl.navy.mil, miquel@df.uba.ar, kkeil@suse.de,
	benh@kernel.crashing.org, video4linux-list@redhat.com,
	rmk+mmc@arm.linux.org.uk, Neela.Kolli@engenio.com,
	jgarzik@pobox.com, vandrove@vc.cvut.cz, adaplas@pol.net,
	thomas@winischhofer.net, weissg@vienna.at, philb@gnu.org,
	linux-pcmcia@lists.infradead.org, jkmaline@cc.hut.fi,
	paulus@samba.org
Subject: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
Date: Thu, 20 Jul 2006 19:25:16 +0200	[thread overview]
Message-ID: <1153416317.11873.22.camel@hemera> (raw)
In-Reply-To: <44BD9BA8.7070202@cluded.net>

Hi,

On wo, 2006-07-19 at 02:40 +0000, Daniel K. wrote:
> > [...] 
> > diff --git a/drivers/char/rio/riocmd.c b/drivers/char/rio/riocmd.c
> > index 4df6ab2..593940f 100644
> > --- a/drivers/char/rio/riocmd.c
> > +++ b/drivers/char/rio/riocmd.c
> > @@ -556,9 +556,7 @@ struct CmdBlk *RIOGetCmdBlk(void)
> >  {
> >  	struct CmdBlk *CmdBlkP;
> >  
> > -	CmdBlkP = (struct CmdBlk *)kmalloc(sizeof(struct CmdBlk), GFP_ATOMIC);
> > -	if (CmdBlkP)
> > -		memset(CmdBlkP, 0, sizeof(struct CmdBlk));
> > +	CmdBlkP = kzalloc(sizeof(struct CmdBlk), GFP_ATOMIC);
> >  	return CmdBlkP;
> >  }
> >  
> 
> Why not return kzalloc(...) here? Alternatively, return (type *) kzalloc(...),
> if you believe in explicit type casting of void pointers.
I figured someone might want to add extra code in f.e. RIOGetCmddBlk to
be able to debug/modify memory allocation behavior for the RIO driver
only. It does look a bit messy though. So I've updated it in my updated
patch.

Cheers,
Takis


  parent reply	other threads:[~2006-07-20 17:25 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19  0:46 [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc Panagiotis Issaris
2006-07-19  0:59 ` Alexey Dobriyan
2006-07-19  1:38   ` Panagiotis Issaris
2006-07-19  2:40 ` Daniel K.
2006-07-19  8:38   ` Pekka Enberg
2006-07-20 17:25   ` Panagiotis Issaris [this message]
2006-07-20 17:49     ` Pekka Enberg
2006-07-19 12:17 ` Antonino A. Daplas
2006-07-19 12:52 ` Paul Mackerras
2006-07-19 13:53   ` Pekka Enberg
2006-07-19 13:53 ` Paulo Marques
2006-07-20 18:03   ` Panagiotis Issaris
  -- strict thread matches above, loose matches on Subject: below --
2006-07-20 19:05 Panagiotis Issaris
2006-07-21  6:50 ` Rolf Eike Beer
2006-07-21  6:58   ` Pekka Enberg
2006-07-21  7:05     ` Jeff Garzik
2006-07-21  9:09       ` Stefan Richter
2006-07-21 10:20         ` Jesper Juhl
2006-07-21 10:35           ` Panagiotis Issaris
2006-07-21 10:38             ` Pekka J Enberg
2006-07-21 10:55               ` Stefan Richter
2006-07-22 17:58                 ` Tomasz Kłoczko
2006-07-22 18:25                   ` Stefan Richter
2006-07-22 18:35                     ` Tomasz Kłoczko
2006-07-22 20:02                       ` Jeff Garzik
2006-07-22 20:55                         ` Tomasz Kłoczko
2006-07-23 11:20                           ` Alexey Dobriyan
2006-07-23 17:55                             ` Tomasz Kłoczko
2006-07-23 18:24                               ` Michael Buesch
2006-07-24  0:10                                 ` Tomasz Kłoczko
2006-07-24  0:49                                   ` Tomasz Kłoczko
2006-07-23 15:16                         ` Stefan Richter
2006-07-23 18:09                           ` Tomasz Kłoczko
2006-07-21 10:53           ` Stefan Richter
2006-07-21 11:09             ` Stefan Richter
2006-07-21 21:16           ` Jeff Garzik
2006-07-21 21:15         ` Jeff Garzik
2006-07-22  6:20           ` Stefan Richter
2006-07-21 10:21   ` Daniel K.
2006-07-21 10:30   ` Panagiotis Issaris
2006-07-21 11:12     ` Rolf Eike Beer
2006-07-21 12:35 ` Dmitry Torokhov
2006-07-21 12:39   ` Panagiotis Issaris
2006-07-22  2:22 Brown, Len

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=1153416317.11873.22.camel@hemera \
    --to=takis@gna.org \
    --cc=Neela.Kolli@engenio.com \
    --cc=adaplas@pol.net \
    --cc=benh@kernel.crashing.org \
    --cc=chas@cmf.nrl.navy.mil \
    --cc=daniel@cluded.net \
    --cc=jgarzik@pobox.com \
    --cc=jkmaline@cc.hut.fi \
    --cc=kkeil@suse.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=miquel@df.uba.ar \
    --cc=paulus@samba.org \
    --cc=philb@gnu.org \
    --cc=rmk+mmc@arm.linux.org.uk \
    --cc=takis@lumumba.uhasselt.be \
    --cc=thomas@winischhofer.net \
    --cc=vandrove@vc.cvut.cz \
    --cc=video4linux-list@redhat.com \
    --cc=weissg@vienna.at \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox