DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: peichao85@gmail.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Remove duplicated lines in memzone_reserve_aligned_thread_unsafe
Date: Thu, 2 Jan 2014 16:10:50 +0100	[thread overview]
Message-ID: <201401021610.50548.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1388667942-10198-1-git-send-email-peichao85@gmail.com>

02/01/2014 14:05, peichao85@gmail.com :
> 
> Remove duplicated lines when reserving memory zone.
> 
> Signed-off-by: Pei Chao <peichao85@gmail.com>

Acked and applied in 1.5.1r2 with this log:

    mem: remove duplicated lines
    
    Extra space for future alignment was reserved twice.
    It was introduced in version 1.3.0 (commit 916e4f4f4e45a1d3cdd473cf9ef).


Thanks for your patch

-- 
Thomas

      reply	other threads:[~2014-01-02 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 13:05 peichao85
2014-01-02 15:10 ` Thomas Monjalon [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=201401021610.50548.thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=peichao85@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;
as well as URLs for NNTP newsgroup(s).