linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Ji-Hun Kim <ji_hun.kim@samsung.com>
Cc: peterhuewe@gmx.de, tweek@google.com,
	jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca, arnd@arndb.de,
	gregkh@linuxfoundation.org, javierm@redhat.com,
	sonnyrao@chromium.org, enric.balletbo@collabora.com,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/2] tpm: replace kmalloc() + memcpy() with kmemdup()
Date: Thu, 10 May 2018 05:16:43 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1805100516350.12749@namei.org> (raw)
In-Reply-To: <1525824757-21835-1-git-send-email-ji_hun.kim@samsung.com>

On Wed, 9 May 2018, Ji-Hun Kim wrote:

> Use kmemdup rather than duplicating its implementation.
> 
> Signed-off-by: Ji-Hun Kim <ji_hun.kim@samsung.com>


Reviewed-by: James Morris <james.morris@microsoft.com>


-- 
James Morris
<jmorris@namei.org>

  parent reply	other threads:[~2018-05-09 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180509001258epcas1p4e8db163d8babd90284dd6afb6a96eb0f@epcas1p4.samsung.com>
2018-05-09  0:12 ` [PATCH 1/2] tpm: replace kmalloc() + memcpy() with kmemdup() Ji-Hun Kim
     [not found]   ` <CGME20180509001300epcas2p3971900d48408aef6a80f59b9480aac16@epcas2p3.samsung.com>
2018-05-09  0:12     ` [PATCH 2/2] " Ji-Hun Kim
2018-05-09 19:16       ` James Morris
2018-05-14 10:58       ` Jarkko Sakkinen
2018-05-09 19:16   ` James Morris [this message]
2018-05-14 10:58   ` [PATCH 1/2] " Jarkko Sakkinen

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=alpine.LRH.2.21.1805100516350.12749@namei.org \
    --to=jmorris@namei.org \
    --cc=arnd@arndb.de \
    --cc=enric.balletbo@collabora.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=javierm@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=ji_hun.kim@samsung.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=sonnyrao@chromium.org \
    --cc=tweek@google.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).