virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mayhs11saini@gmail.com
Cc: netdev@vger.kernel.org,
	virtualization@lists.linux-foundation.org, mst@redhat.com
Subject: Re: [PATCH] net: Use kmemdup instead of kmalloc and memcpy
Date: Tue, 27 Dec 2016 20:16:47 -0500 (EST)	[thread overview]
Message-ID: <20161227.201647.338740723131819171.davem@davemloft.net> (raw)
In-Reply-To: <1482520498-28259-1-git-send-email-mayhs11saini@gmail.com>

From: Shyam Saini <mayhs11saini@gmail.com>
Date: Sat, 24 Dec 2016 00:44:58 +0530

> when some other buffer is immediately copied into allocated region.
> Replace calls to kmalloc followed by a memcpy with a direct
> call to kmemdup.
> 
> Signed-off-by: Shyam Saini <mayhs11saini@gmail.com>

Applied.

       reply	other threads:[~2016-12-28  1:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1482520498-28259-1-git-send-email-mayhs11saini@gmail.com>
2016-12-28  1:16 ` David Miller [this message]
2016-12-23 19:14 [PATCH] net: Use kmemdup instead of kmalloc and memcpy Shyam Saini

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=20161227.201647.338740723131819171.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=mayhs11saini@gmail.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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).