From: Takashi Iwai <tiwai@suse.de>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: asihpi - use kzalloc()
Date: Sun, 07 Aug 2011 17:33:17 +0200 [thread overview]
Message-ID: <s5hr54x9qyq.wl%tiwai@suse.de> (raw)
In-Reply-To: <1312629983.5589.129.camel@localhost.localdomain>
At Sat, 06 Aug 2011 13:26:20 +0200,
Thomas Meyer wrote:
>
> From: Thomas Meyer <thomas@m3y3r.de>
>
>
> Use kzalloc rather than kmalloc followed by memset with 0
>
> This considers some simple cases that are common and easy to validate
> Note in particular that there are no ...s in the rule, so all of the
> matched code has to be contiguous
>
> The semantic patch that makes this output is available
> in scripts/coccinelle/api/alloc/kzalloc-simple.cocci.
>
> More information about semantic patching is available at
> http://coccinelle.lip6.fr/
>
> Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
Applied now. Thanks.
Takashi
> ---
>
> diff -u -p a/sound/pci/asihpi/hpicmn.c b/sound/pci/asihpi/hpicmn.c
> --- a/sound/pci/asihpi/hpicmn.c 2011-07-26 00:46:12.970154018 +0200
> +++ b/sound/pci/asihpi/hpicmn.c 2011-08-01 20:42:34.859285236 +0200
> @@ -631,13 +631,12 @@ struct hpi_control_cache *hpi_alloc_cont
> if (!p_cache)
> return NULL;
>
> - p_cache->p_info =
> - kmalloc(sizeof(*p_cache->p_info) * control_count, GFP_KERNEL);
> + p_cache->p_info = kzalloc(sizeof(*p_cache->p_info) * control_count,
> + GFP_KERNEL);
> if (!p_cache->p_info) {
> kfree(p_cache);
> return NULL;
> }
> - memset(p_cache->p_info, 0, sizeof(*p_cache->p_info) * control_count);
> p_cache->cache_size_in_bytes = size_in_bytes;
> p_cache->control_count = control_count;
> p_cache->p_cache = p_dsp_control_buffer;
>
>
>
prev parent reply other threads:[~2011-08-07 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 11:26 Thomas Meyer
2011-08-07 15:33 ` Takashi Iwai [this message]
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=s5hr54x9qyq.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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
all inboxes | Powered by JetHome®