From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: linux-s390@vger.kernel.org
Subject: Re: [PATCH -next] s390/pci: use kmem_cache_zalloc instead of kmem_cache_alloc/memset
Date: Thu, 28 Feb 2013 12:50:01 +0000 [thread overview]
Message-ID: <20130228125000.GC4819@osiris> (raw)
In-Reply-To: <CAPgLHd_ioTOW81brF-Yk9ssx2nXrFcbOShqHP+AsFyWyoUqe3A@mail.gmail.com>
On Mon, Feb 25, 2013 at 10:09:25PM +0800, Wei Yongjun wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> Using kmem_cache_zalloc() instead of kmem_cache_alloc() and memset().
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
[...]
> - zdev->fmb = kmem_cache_alloc(zdev_fmb_cache, GFP_KERNEL);
> + zdev->fmb = kmem_cache_zalloc(zdev_fmb_cache, GFP_KERNEL);
> if (!zdev->fmb)
> return -ENOMEM;
> - memset(zdev->fmb, 0, sizeof(*zdev->fmb));
> WARN_ON((u64) zdev->fmb & 0xf);
Applied. Thanks!
next parent reply other threads:[~2013-02-28 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPgLHd_ioTOW81brF-Yk9ssx2nXrFcbOShqHP+AsFyWyoUqe3A@mail.gmail.com>
2013-02-28 12:50 ` Heiko Carstens [this message]
[not found] <CAPgLHd-wy1eaf0OjxHeho3Lo3ADBt=oKsU7pGR0vpbHvHiCkjg@mail.gmail.com>
2012-12-03 16:02 ` [PATCH -next] s390/pci: use kmem_cache_zalloc instead of kmem_cache_alloc/memset Martin Schwidefsky
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=20130228125000.GC4819@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
/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