From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v9 00/10] eal: replace calls to rte_panic and refrain from new instances Date: Fri, 27 Apr 2018 18:40:24 +0200 Message-ID: <2687436.XNaodg91aW@xps> References: <1524663944-30376-11-git-send-email-arnon@qwilt.com> <2992884.f5kbt66Nfe@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: anatoly.burakov@intel.com, bruce.richardson@intel.com, declan.doherty@intel.com, dev@dpdk.org, ferruh.yigit@intel.com, jerin.jacob@caviumnetworks.com, wenzhuo.lu@intel.com To: Arnon Warshavsky Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 9BB958DB4 for ; Fri, 27 Apr 2018 18:40:28 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 27/04/2018 18:31, Arnon Warshavsky: > On Fri, Apr 27, 2018, 17:22 Thomas Monjalon wrote: > > What is the status of this patchset? > > It seems not ready for RC1 (today). > > I don't want to push it in RC2 because it changes too many things. > > So it's today or wait for 18.08. What do you think? > > > > The last patch for check tooling can be separated and pushed at anytime. > > > > Yes,unfortunately its 18.08.I am away the entire weekend from any means of > getting the code fixed, so only on Sunday I will split the last patch from > the rest. So you are OK with considering this patchset for 18.08? And take the tool in 18.05? > Should I put the tooling patch as a new set and refer both patchsets to the > current v9? Yes you can split and keep v9 numbering for both.