From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 39B241B1F6 for ; Wed, 2 Jan 2019 10:21:14 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jan 2019 01:21:13 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,430,1539673200"; d="scan'208";a="122621388" Received: from dpdk-tbie.sh.intel.com ([10.67.104.173]) by orsmga002.jf.intel.com with ESMTP; 02 Jan 2019 01:21:12 -0800 Date: Wed, 2 Jan 2019 17:19:00 +0800 From: Tiwei Bie To: Hideyuki Yamashita Cc: "Burakov, Anatoly" , dev@dpdk.org, Yasufumi Ogawa , Nakamura Hioryuki , maxime.coquelin@redhat.com, zhihong.wang@intel.com Message-ID: <20190102091900.GA12203@dpdk-tbie.sh.intel.com> References: <201812181131.wBIBVX8p018158@ccmail04.silk.ntt-tx.co.jp> <20181218130901.GB2464@dpdk-tbie.sh.intel.com> <201812270554.wBR5rnsV005042@ccmail04.silk.ntt-tx.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <201812270554.wBR5rnsV005042@ccmail04.silk.ntt-tx.co.jp> User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] rte_eal_hotplug_remove() generates error message 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: , X-List-Received-Date: Wed, 02 Jan 2019 09:21:15 -0000 On Thu, Dec 27, 2018 at 02:52:17PM +0900, Hideyuki Yamashita wrote: > Q1. > I CCed my patch to stable@dpdk.org > Is that mean it will be reflected into 18.11 stable release? Yes. > The reason why I ask this is I think it is better that bug should > be reflected into LTS because I and SPP users mainly use DPDK LTS(18.11). > > Q2. > If yes, when will those stable release will be released? > (e.g. once a month ) Plans can be found here: https://core.dpdk.org/roadmap/#stable > > Q3. > I understand my patch is acked and merged into > dpdk-next-virtio. > What is dpdk-next-virtio? > It is the branch which will be reflected into next release? It's already in main repo now: http://git.dpdk.org/dpdk/commit/drivers/net/vhost?id=6e3339ca07734e59cd0c24594e3014ab49a0ffc0