From: Alan Cox <alan@linux.intel.com>
To: Hari Prasath <gehariprasath@gmail.com>, mchehab@kernel.org
Cc: gregkh@linuxfoundation.org, rvarsha016@gmail.com,
julia.lawall@lip6.fr, singhalsimran0@gmail.com,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: atomisp: replace kmalloc & memcpy with kmemdup
Date: Fri, 07 Jul 2017 12:55:51 +0100 [thread overview]
Message-ID: <1499428551.5590.15.camel@linux.intel.com> (raw)
In-Reply-To: <20170707115044.21744-1-gehariprasath@gmail.com>
On Fri, 2017-07-07 at 17:20 +0530, Hari Prasath wrote:
> kmemdup can be used to replace kmalloc followed by a memcpy.This was
> pointed out by the coccinelle tool.
And kstrdup could do the job even better I think ?
Alan
next prev parent reply other threads:[~2017-07-07 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 11:50 [PATCH] staging: atomisp: replace kmalloc & memcpy with kmemdup Hari Prasath
2017-07-07 11:55 ` Alan Cox [this message]
2017-07-07 13:22 ` hari prasath
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=1499428551.5590.15.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gehariprasath@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rvarsha016@gmail.com \
--cc=singhalsimran0@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.