public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Dumbre, Nitesh Dilip (N.)" <ndumbre@visteon.com>
Cc: "oleg.drokin@intel.com" <oleg.drokin@intel.com>,
	"andreas.dilger@intel.com" <andreas.dilger@intel.com>,
	"Julia.Lawall@lip6.fr" <Julia.Lawall@lip6.fr>,
	"joe@perches.com" <joe@perches.com>,
	"gdonald@gmail.com" <gdonald@gmail.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"rickard_strandqvist@spectrumdigital.se" 
	<rickard_strandqvist@spectrumdigital.se>,
	"uja.ornl@gmail.com" <uja.ornl@gmail.com>,
	"john.hammond@intel.com" <john.hammond@intel.com>,
	"HPDD-discuss@lists.01.org" <HPDD-discuss@ml01.01.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: Replace kzalloc and memcpy by kmemdup
Date: Sun, 31 May 2015 11:35:09 +0900	[thread overview]
Message-ID: <20150531023509.GC13103@kroah.com> (raw)
In-Reply-To: <20150520070418.GA28946@jci-VirtualBox>

On Wed, May 20, 2015 at 07:04:27AM +0000, Dumbre, Nitesh Dilip (N.) wrote:
> This patch was generated by coccicheck and replaces kzalloc followed
> by memcpy with kmemdup
> 
> Signed-off-by: Nitesh Dumbre <ndumbre@visteon.com>

Name doesn't match the From: line, please fix your broken email client.

WHat is up with this company's email, there is a bunch of patches from
different people, all of them broken like this.

greg k-h

  parent reply	other threads:[~2015-05-31  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  7:04 [PATCH] staging: Replace kzalloc and memcpy by kmemdup Dumbre, Nitesh Dilip (N.)
2015-05-20  7:54 ` Drokin, Oleg
2015-05-31  2:35 ` gregkh [this message]
2015-05-31 13:13   ` Joe Perches
2015-05-31 20:56     ` gregkh

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=20150531023509.GC13103@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=Julia.Lawall@lip6.fr \
    --cc=akpm@linux-foundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gdonald@gmail.com \
    --cc=joe@perches.com \
    --cc=john.hammond@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndumbre@visteon.com \
    --cc=oleg.drokin@intel.com \
    --cc=rickard_strandqvist@spectrumdigital.se \
    --cc=uja.ornl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox