All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH 0/2] Introduce l_memdup function
Date: Fri, 16 Jan 2015 10:50:04 -0600	[thread overview]
Message-ID: <54B9413C.1080804@gmail.com> (raw)
In-Reply-To: <1421399632-19544-1-git-send-email-jukka.rissanen@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

Hi Jukka,

On 01/16/2015 03:13 AM, Jukka Rissanen wrote:
> Hi,
>
> this patch introduces new l_memdup() function in patch 1.
>
> The new function is then used in patch 2. The genl.c was the only
> place in the code base where such a change could be done (at least I
> could not spot any other place having malloc+memcpy in the code after
> quick review).
>
> Cheers,
> Jukka
>

Both applied, thanks.

Regards,
-Denis

      parent reply	other threads:[~2015-01-16 16:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16  9:13 [PATCH 0/2] Introduce l_memdup function Jukka Rissanen
2015-01-16  9:13 ` [PATCH 1/2] util: Add l_memdup function for allocation and copying a memory buffer Jukka Rissanen
2015-01-16  9:13 ` [PATCH 2/2] genl: Convert l_malloc + memcpy to use l_memdup Jukka Rissanen
2015-01-16 16:50 ` Denis Kenzior [this message]

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=54B9413C.1080804@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ell@lists.01.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 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.