From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D282121BBD; Fri, 27 Apr 2018 12:40:26 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 27 Apr 2018 12:40:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=KbeLK5gmtf5l9fBwXWXCJtnn+M t6syk+kmHohqzsRwA=; b=JL8LgBid39Ng+q6mnyBhaHiYXTdcaz0gLoaU1slDRz 4FZITBSaOlLpgNKmmHzaIflsrv+LyYCWpp84iRHHbFOgmsL+EampuMo44W2JJN+j j5JCKHg0wAO82+iuxxqC5GV8jr5JLG7ZUoXHdCoDjZ2hA8GFqTpYOAnwz3NOjzwu w= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=KbeLK5 gmtf5l9fBwXWXCJtnn+Mt6syk+kmHohqzsRwA=; b=Inx9swkQTGFRghQsPv/UEe slop4AlfhGgMaanqVVQXFJD1q6JsFrBcjUmwUAj47Hck0kIqzKtB0LzMHOL3Wr8i D4T9fiM+sKxWhRpxYZ1gUacnJqRzesXgtsYvi2wNBZbOWl01OPwH3OWG6uzprzkH pcdYQMjVp1clmJG3COpdHa2Hj+HC23evzcEr8c/MdVACpWED3KkFNiKfzCTg74Nj vIz11OsC9zMHSO4ULxbuC+qEtjFDc+4NQJMQ96gSnwhq6JumLz8U6qKF3GziCg7W rCTcNFWJ9XjJ0yt54KCQEi4q0AtgqMAl++rUwJP+wtPQThMPm/bRXQ/2HqCU8w/A == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B1623E4412; Fri, 27 Apr 2018 12:40:25 -0400 (EDT) From: Thomas Monjalon To: Arnon Warshavsky 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 Date: Fri, 27 Apr 2018 18:40:24 +0200 Message-ID: <2687436.XNaodg91aW@xps> In-Reply-To: References: <1524663944-30376-11-git-send-email-arnon@qwilt.com> <2992884.f5kbt66Nfe@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v9 00/10] eal: replace calls to rte_panic and refrain from new instances 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: Fri, 27 Apr 2018 16:40:28 -0000 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.