From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 83B19A045E for ; Wed, 29 May 2019 18:32:58 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 780CC1B970; Wed, 29 May 2019 18:32:58 +0200 (CEST) Received: by dpdk.org (Postfix, from userid 1017) id 098201B970; Wed, 29 May 2019 18:32:57 +0200 (CEST) In-Reply-To: <6473125811ac8ed499079652b7f3c32907155fc9.1559147228.git.anatoly.burakov@intel.com> References: <6473125811ac8ed499079652b7f3c32907155fc9.1559147228.git.anatoly.burakov@intel.com> To: test-report@dpdk.org Cc: Anatoly Burakov Message-Id: <20190529163257.098201B970@dpdk.org> Date: Wed, 29 May 2019 18:32:57 +0200 (CEST) From: checkpatch@dpdk.org Subject: [dpdk-test-report] |WARNING| pw53829 [PATCH 01/25] eal: add API to lock/unlock memory hotplug X-BeenThere: test-report@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: automatic DPDK test reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: test-report-bounces@dpdk.org Sender: "test-report" Test-Label: checkpatch Test-Status: WARNING http://dpdk.org/patch/53829 _coding style issues_ ERROR: symbol rte_eal_mcfg_mem_read_lock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map ERROR: symbol rte_eal_mcfg_mem_read_unlock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map ERROR: symbol rte_eal_mcfg_mem_write_lock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map ERROR: symbol rte_eal_mcfg_mem_write_unlock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map