From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A5F5CA04DD; Wed, 28 Oct 2020 13:09:06 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 88F93CB63; Wed, 28 Oct 2020 13:09:04 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id A92B2CB41; Wed, 28 Oct 2020 13:09:01 +0100 (CET) IronPort-SDR: tsfG81iSkKgNv4Si1t/p/fWsQLQ5b5MEGGNtX55a4rib0Z1U5B37kgfsOHlJVVKIyCyWfNH+jc Nii9dKuUMxaQ== X-IronPort-AV: E=McAfee;i="6000,8403,9787"; a="167466084" X-IronPort-AV: E=Sophos;i="5.77,426,1596524400"; d="scan'208";a="167466084" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2020 05:09:00 -0700 IronPort-SDR: jPuYCyUSdsEMHuA0L3glMZSK/me5rx+JXc3U3WGr8EF24AwY5D0+Qv7p4XelaT5rUFrGAJ4qPA lbvneHHwvxQQ== X-IronPort-AV: E=Sophos;i="5.77,426,1596524400"; d="scan'208";a="350972455" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.213.193.36]) ([10.213.193.36]) by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2020 05:08:58 -0700 To: Thomas Monjalon , dev@dpdk.org Cc: ferruh.yigit@intel.com, david.marchand@redhat.com, bruce.richardson@intel.com, olivier.matz@6wind.com, ciara.power@intel.com, akhil.goyal@nxp.com, fiona.trahe@intel.com, john.griffin@intel.com, deepak.k.jain@intel.com, stable@dpdk.org References: <20201022220525.1532249-1-thomas@monjalon.net> <20201022220525.1532249-3-thomas@monjalon.net> From: "Burakov, Anatoly" Message-ID: <44ed932e-c649-2b0e-e974-64d092aa1a37@intel.com> Date: Wed, 28 Oct 2020 12:08:56 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <20201022220525.1532249-3-thomas@monjalon.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH 2/5] mem: fix config name in error logs X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 22-Oct-20 11:05 PM, Thomas Monjalon wrote: > When introducing the new option CONFIG_RTE_MAX_MEM_MB_PER_TYPE, > some logs were referencing a wrong name: CONFIG_RTE_MAX_MEM_PER_TYPE. > > Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists") > Cc: stable@dpdk.org > > Signed-off-by: Thomas Monjalon > --- Acked-by: Anatoly Burakov -- Thanks, Anatoly