From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 17516AAC9 for ; Sat, 2 Jun 2018 07:13:50 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A92EE21B82; Sat, 2 Jun 2018 01:13:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sat, 02 Jun 2018 01:13:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fridaylinux.org; h=cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=pX/2fFJknQqLYFrDKvs398dBPCzr1rP0604EpkyoDY4=; b=TRo3cGOO fv//hLt33ROkTb+3P/btngVShgQaW8t77ljOtOzJ04JJh10lP/2TJV8wlds6fi8n sndx1VoC5DytW6dqMkBdSbxq3jFWsGPPxb2h3oyCBfWX2ceaoHdiYz7zPt9Wip2O 5C55VcENHtbem4oDf5nHPj0l53hz8u9VI77iS5/LNA3zY5N3nCHszma3sIkeLdfo sa14KIrUAQ0GauJUki/mN4x7x/Vj0H9/fyLRnEjhQMZi/e4YYxI3RI9hyKFOk5ok hYwgu2AIU0UQDZgf7h1OiAmIqQLThb/36LwMUKFNXKJMtB9KzR6V0CRCUPqiff7c Vb7uMAXzNdz0sQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=pX/2fFJknQqLYFrDKvs398dBPCzr1 rP0604EpkyoDY4=; b=BLzH3bZIqwMWBkCAaar5KK3f/c6KwZSY06yBPSNHymThH gZx2kEjnKiR3mV66IvgzMsKVs3aoiC+29A8RyrMntaD63Z2q9R9Jgbjbamfh2zi3 KzduVZEBp9GGg8kgj+5irS+nJU+Mk1PCdWdqhZQkn8Vxj6xhJ9yOSfenZRxMjfDY CeCVnAO0uJk7IBu0Jt926RqRzeaMzKr0eNbnJKbimQ9T4xWY587zNjPYfZa4OtIo F9bfKzUQqvC/EnBoaIl6G7SGUZW3LZbaPvr+E7I3Fc82vRX4HSTu7WD9vvWPfsMM dUz5KtFBBHYQ6hdfa/AwMjV6PrAOVAJS85b/FYghw== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from yuanhanliu-NB0 (unknown [223.74.148.12]) by mail.messagingengine.com (Postfix) with ESMTPA id C9961E4D72; Sat, 2 Jun 2018 01:13:48 -0400 (EDT) Date: Sat, 2 Jun 2018 13:13:34 +0800 From: Yuanhan Liu To: Thomas Monjalon Cc: Kevin Traynor , bluca@debian.org, Yongseok Koh , stable@dpdk.org Message-ID: <20180602051334.5vpjgalrfhlfjvk3@yuanhanliu-NB0.tencent.com> References: <20180527053517.lv24ma5n452na3cm@yuanhanliu-NB0.tencent.com> <96ecbff9-7e63-52f0-e765-5b00ff3024e4@redhat.com> <3962613.dM9x5Q0JGJ@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3962613.dM9x5Q0JGJ@xps> User-Agent: NeoMutt/20170113 (1.7.2) Subject: Re: [dpdk-stable] 17.11.3 (LTS) patches review and test X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jun 2018 05:13:50 -0000 On Mon, May 28, 2018 at 12:30:01PM +0200, Thomas Monjalon wrote: > 28/05/2018 12:16, Kevin Traynor: > > These patches which are stable relevant only, need a small fix which is > > here on 18.02 branch: > > http://dpdk.org/browse/dpdk-stable/commit/?h=18.02&id=e89e323e4ce58f2cbbc7afcc2d5dc7ce66075e81 Pushed to dpdk-stable/17.11, thanks for letting me know. > About the process, I wonder what should be the reference branch when backporting. > For example, could we use 18.02 stable branch to backport in 17.11? We normally do (and should) not do that. For fixes not from the master branch, the author should send a patch alone to the stable list, telling the maintainer this patch is stable only and should apply to stable release X, Y, etc. I saw I was on the cc list. It's likely I have missed the patch before, and sorry for that. --yliu