From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: freude@linux.ibm.com, heiko.carstens@de.ibm.com,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/zcrypt: Use kmemdup to replace kmalloc + memcpy
Date: Mon, 10 Sep 2018 08:34:50 +0200 [thread overview]
Message-ID: <20180910083450.62379f4b@mschwideX1> (raw)
In-Reply-To: <1536396621-19363-1-git-send-email-zhongjiang@huawei.com>
On Sat, 8 Sep 2018 16:50:21 +0800
zhong jiang <zhongjiang@huawei.com> wrote:
> kmemdup has implemented the function that kmalloc() + memcpy() will
> do. and we prefer to use the kmemdup rather than the open coded implementation.
>
> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
> ---
> drivers/s390/crypto/zcrypt_msgtype6.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
Applied to linux-390:features. Thanks.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2018-09-10 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 8:50 [PATCH] s390/zcrypt: Use kmemdup to replace kmalloc + memcpy zhong jiang
2018-09-10 6:34 ` Martin Schwidefsky [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=20180910083450.62379f4b@mschwideX1 \
--to=schwidefsky@de.ibm.com \
--cc=freude@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=zhongjiang@huawei.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;
as well as URLs for NNTP newsgroup(s).