From: Dan Carpenter <dan.carpenter@oracle.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Larry Finger <Larry.Finger@lwfinger.net>,
wlanfae <wlanfae@realtek.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192e: Use kzalloc rather than kmalloc
Date: Tue, 8 Nov 2011 22:35:37 +0300 [thread overview]
Message-ID: <20111108193537.GB4682@mwanda> (raw)
In-Reply-To: <1320779160.8062.139.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Tue, Nov 08, 2011 at 08:05:53PM +0100, 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 change 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>
All the patches with the subject "[PATCH] staging: rtl8192e: Use
kzalloc rather than kmalloc" should be combined into a single patch.
Don't do the funny thing where the changelog is indented one space.
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-08 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 19:05 Thomas Meyer
2011-11-08 19:35 ` Dan Carpenter [this message]
2011-11-08 19:17 Thomas Meyer
2011-11-08 19:17 Thomas Meyer
2011-11-08 19:18 Thomas Meyer
2011-11-08 19:29 ` Jesper Juhl
2011-11-08 19:19 Thomas Meyer
2011-11-08 19:20 Thomas Meyer
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=20111108193537.GB4682@mwanda \
--to=dan.carpenter@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
--cc=wlanfae@realtek.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 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®