From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 2D2EDCFA0; Tue, 17 Apr 2018 21:06:45 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C96A421FC4; Tue, 17 Apr 2018 15:06:44 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 17 Apr 2018 15:06:44 -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=nDUJTX8lGaanBOVLHTIWkn7qHw Au6Pc2T3YmEJF4w6M=; b=WhuKRkz/e26FCzLy8A5Fzpqre4lLvEb8eYmiRhDQ5+ TKdSYayEmOoSqNOzrNkQeZnekLbVlR+egczVYRpDgvMQ90fCfhg4DC9+//iFiorX clYusWIqdMhtfaVpOqgVN25uWMYB46M4vQZxaA2Z4l0b6/wiTyKw8ViTu0Dv8rKY Y= 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=nDUJTX 8lGaanBOVLHTIWkn7qHwAu6Pc2T3YmEJF4w6M=; b=C3j7siJNgScCD9DG83tn3n 5qtFFa2asU2nsiO8v6KJBpMJxsv6xe6I+BZCSvwAOJCs3VFr6BQC+Nd//KM7e62f ofMDRwVVeiEhfU8RFDdSRIiOsrBR43bBPOksV9ys4nRox0iVebXQ0LvHy8xt5OFd HrvG09OBhXqEoIxAJ0Obbv3tzRp1hk+/5J6Q7fTjWyntJ/k+LQc5kHBbRc0Fm5bI SP8jRavMXJ8IfSmRIr1oU1+bkm5pyPCExg30y5ncJnXPgFmBvWOrLvl+XrhZmY/x ZEQJNCnVpATmHKM/f0H8VBJ9jH5Jn5izSNgjUvYemvtHzs73mfyWv/a1v6vQF39w == X-ME-Sender: <xms:xEXWWmQlgMz1q3iGflklaiAd4uQIGEkGxq6ftvtPe1qJaIqtnGX47A> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 08AD1E4120; Tue, 17 Apr 2018 15:06:43 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: Alejandro Lucero <alejandro.lucero@netronome.com> Cc: Aaron Conole <aconole@redhat.com>, dev <dev@dpdk.org>, Adrien Mazarguil <adrien.mazarguil@6wind.com>, stable@dpdk.org Date: Tue, 17 Apr 2018 21:06:42 +0200 Message-ID: <6959615.KTR3aUb7BS@xps> In-Reply-To: <CAD+H993MK8rE4g7GEToNhOC9v7CdTXjHm=mE3eqPRsGYgCtZmw@mail.gmail.com> References: <20180412222208.11770-1-aconole@redhat.com> <1787360.RVVfK0dUvc@xps> <CAD+H993MK8rE4g7GEToNhOC9v7CdTXjHm=mE3eqPRsGYgCtZmw@mail.gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [RFC 2/2] nfp: allow for non-root user X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches <stable.dpdk.org> List-Unsubscribe: <https://dpdk.org/ml/options/stable>, <mailto:stable-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/stable/> List-Post: <mailto:stable@dpdk.org> List-Help: <mailto:stable-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/stable>, <mailto:stable-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 17 Apr 2018 19:06:45 -0000 17/04/2018 18:24, Alejandro Lucero: > On Tue, Apr 17, 2018 at 4:54 PM, Thomas Monjalon <thomas@monjalon.net> > wrote: > > > 17/04/2018 17:44, Alejandro Lucero: > > > Adding stable@ and Thomas for discussing how can this be added to stable > > > DPDK versions even if this is not going to be a patch for current DPDK > > > version. > > > > I don't understand. > > This patch won't enter in 18.05? > > Why do you think this patch is candidate for stable but not master? > > > Because all that code has been removed between 18.02 and 18.05: > > http://dpdk.org/ml/archives/dev/2018-March/093655.html > > I guess this had not happen yet, and stable versions only pull patches from > vanilla. Am I right? Yes patches are cherry-picked from master. But when the backport is too much difficult, a patch can be sent directly to stable@dpdk.org. I don't know whether it already happened to fix a removed code. You need to make sure that the maintainers of stable branches will pick it. There is no special process, it's all a matter of communication :)