All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Rolf Eike Beer <eike-kernel@sf-tec.de>,
	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,
	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: Fri, 21 Jul 2006 17:15:38 -0400	[thread overview]
Message-ID: <44C143FA.9030808@pobox.com> (raw)
In-Reply-To: <44C099D2.5030300@s5r6.in-berlin.de>

Stefan Richter wrote:
> Jeff Garzik wrote:
>> Pekka Enberg wrote:
>>> On 7/21/06, Rolf Eike Beer <eike-kernel@sf-tec.de> wrote:
>>>>> -     if (!(handle = kmalloc(sizeof(struct input_handle), GFP_KERNEL)))
>>>>> +     handle = kzalloc(sizeof(struct input_handle), GFP_KERNEL);
>>>>> +     if (!handle)
>>>>>               return NULL;
>>>> sizeof(*handle)?
>>> In general, yes. However, some maintainers don't like that, so I would
>>> recommend to keep them as-is unless you get a clear ack from the
>>> maintainer to change it.
> 
> I suggest:
>  - check if "sizeof(type)"->"sizeof(*ptr)" is correct
>  - if yes, change it
>  - do this for all kmalloc + kzalloc in a file you touched, or
>    better yet for all kmalloc + kzalloc in a driver or subsystem you
>    touched

This breaks the rules of standard Linux patches.

The patch should contain ONE logical change.  Any cleanups such as 
sizeof(type) -> sizeof(*ptr) should be in a SEPARATE PATCH.

	Jeff



  parent reply	other threads:[~2006-07-21 21:16 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-20 19:05 [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc 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-24  8:03                                     ` Lindent cleanup (was Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.) Stefan Richter
2006-07-24  8:52                                       ` Tomasz Kłoczko
2006-07-23 15:16                         ` [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc 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 [this message]
2006-07-22  6:20           ` Stefan Richter
2006-07-21  9:32       ` [PATCH] drivers: Conversions from kmalloc+memset tok(z|c)alloc Panagiotis Issaris
2006-07-21 10:14         ` Pekka J Enberg
2006-07-21 10:42           ` Panagiotis Issaris
2006-07-21 11:02           ` Stefan Richter
2006-07-21 11:20             ` Pekka J Enberg
2006-07-21 14:08               ` Stefan Richter
2006-07-21 21:17           ` Jeff Garzik
2006-07-21 10:21   ` [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc 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
  -- strict thread matches above, loose matches on Subject: below --
2006-07-22  2:22 Brown, Len
2006-07-19  0:46 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
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

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=44C143FA.9030808@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Neela.Kolli@engenio.com \
    --cc=adaplas@pol.net \
    --cc=benh@kernel.crashing.org \
    --cc=chas@cmf.nrl.navy.mil \
    --cc=eike-kernel@sf-tec.de \
    --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=penberg@cs.helsinki.fi \
    --cc=philb@gnu.org \
    --cc=rmk+mmc@arm.linux.org.uk \
    --cc=stefanr@s5r6.in-berlin.de \
    --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 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.