From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sergio.gonzalez.monroy@intel.com>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
 by dpdk.org (Postfix) with ESMTP id 9650B6A87
 for <dev@dpdk.org>; Thu, 16 Jul 2015 12:39:28 +0200 (CEST)
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
 by fmsmga102.fm.intel.com with ESMTP; 16 Jul 2015 03:39:28 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.15,487,1432623600"; d="scan'208";a="763707057"
Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.220.29])
 ([10.237.220.29])
 by fmsmga002.fm.intel.com with ESMTP; 16 Jul 2015 03:39:27 -0700
Message-ID: <55A789DD.2060204@intel.com>
Date: Thu, 16 Jul 2015 11:39:25 +0100
From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Thomas Monjalon <thomas.monjalon@6wind.com>
References: <1436977948-589-10-git-send-email-sergio.gonzalez.monroy@intel.com>
 <1437032231-5127-1-git-send-email-sergio.gonzalez.monroy@intel.com>
 <1689589.AfOYY5ubPi@xps13>
In-Reply-To: <1689589.AfOYY5ubPi@xps13>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v11] doc: update malloc documentation
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2015 10:39:29 -0000

On 16/07/2015 11:12, Thomas Monjalon wrote:
> 2015-07-16 08:37, Sergio Gonzalez Monroy:
>> Update malloc documentation to reflect new implementation details.
> Should you reword the memzone chapter and move it after the malloc one?
I didn't think that the memzone doc needed to change its wording for 
this change.

memzone doc in general could be improve and extended but I'd prefer to 
do that as
a post-patch if it needs to be.

Sergio