From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geliang Tang <geliangtang@163.com>
Cc: Sudeep Dutt <sudeep.dutt@intel.com>,
Nikhil Rao <nikhil.rao@intel.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: mic: use kstrdup() in mic_sysfs
Date: Sun, 4 Oct 2015 12:56:14 +0100 [thread overview]
Message-ID: <20151004115614.GA29316@kroah.com> (raw)
In-Reply-To: <6736b3e4fdc27575cf85503eefe7d0c1aaaced33.1443753647.git.geliangtang@163.com>
On Fri, Oct 02, 2015 at 10:43:34AM +0800, Geliang Tang wrote:
> Use kstrdup instead of kmalloc and strncpy.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
> drivers/misc/mic/host/mic_sysfs.c | 23 ++++-------------------
> 1 file changed, 4 insertions(+), 19 deletions(-)
This file isn't even in the tree anymore :(
next prev parent reply other threads:[~2015-10-04 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 2:43 [PATCH] misc: mic: use kstrdup() in mic_sysfs Geliang Tang
2015-10-04 11:56 ` Greg Kroah-Hartman [this message]
2015-10-10 11:46 ` [PATCH] misc: mic: use kstrdup() in cosm_sysfs Geliang Tang
2015-10-10 19:14 ` Joe Perches
2015-10-11 1:01 ` Ashutosh Dixit
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=20151004115614.GA29316@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ashutosh.dixit@intel.com \
--cc=geliangtang@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=sudeep.dutt@intel.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.