From: Martin Schwidefsky <schwidefsky@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: Mon, 03 Dec 2012 16:02:18 +0000 [thread overview]
Message-ID: <20121203110218.3f1c9136@mschwide> (raw)
In-Reply-To: <CAPgLHd-wy1eaf0OjxHeho3Lo3ADBt=oKsU7pGR0vpbHvHiCkjg@mail.gmail.com>
On Mon, 3 Dec 2012 08:07:27 -0500
Wei Yongjun <weiyj.lk@gmail.com> 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>
Added to the features branch of the s390 tree. Thanks.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next parent reply other threads:[~2012-12-03 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPgLHd-wy1eaf0OjxHeho3Lo3ADBt=oKsU7pGR0vpbHvHiCkjg@mail.gmail.com>
2012-12-03 16:02 ` Martin Schwidefsky [this message]
[not found] <CAPgLHd_ioTOW81brF-Yk9ssx2nXrFcbOShqHP+AsFyWyoUqe3A@mail.gmail.com>
2013-02-28 12:50 ` [PATCH -next] s390/pci: use kmem_cache_zalloc instead of kmem_cache_alloc/memset Heiko Carstens
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=20121203110218.3f1c9136@mschwide \
--to=schwidefsky@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