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 DE505A32A3 for ; Fri, 25 Oct 2019 14:20:53 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 148001C138; Fri, 25 Oct 2019 14:20:51 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id ABE9C1C133 for ; Fri, 25 Oct 2019 14:20:49 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Oct 2019 05:20:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.68,228,1569308400"; d="scan'208";a="210706992" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.104]) ([10.237.220.104]) by orsmga002.jf.intel.com with ESMTP; 25 Oct 2019 05:20:47 -0700 To: han.li1@zte.com.cn, thomas@monjalon.net Cc: david.marchand@redhat.com, dev@dpdk.org References: <201910251937435842069@zte.com.cn> From: "Burakov, Anatoly" Message-ID: <930ae82b-bb2f-7b70-317a-d801dca4fda6@intel.com> Date: Fri, 25 Oct 2019 13:20:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <201910251937435842069@zte.com.cn> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v3] lib/librte_eal/linuxapp: fix runtime configmmap issue 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 25-Oct-19 12:37 PM, han.li1@zte.com.cn wrote: > it seems your patch is later then mine? > you rejected mine patch and then committed yours? > I can't understand.... > Hi, Apologies for the confusion. My patch's v1 was sent in July this year, much earlier than yours: http://patches.dpdk.org/project/dpdk/list/?series=5813&state=%2A&archive=both And it's a more general patch, that also fixes the issue for FreeBSD. This is the patch that got committed - it came in first, and it fixes the issue in a more general way, for Linux and for FreeBSD. It's just that for some reason i was under the impression that it was already accepted, but it was merely deferred till 19.11. Again, my apologies for the confusion. I should have looked at your patch more closely. -- Thanks, Anatoly