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 55F531B2F2 for ; Tue, 16 Jan 2018 18:36:20 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 007FE20B7E; Tue, 16 Jan 2018 12:36:19 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 16 Jan 2018 12:36:20 -0500 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=ipFoRnhBPTvfnKLtvi231+jsT+ 4CiCHwWwl5ipxlZDM=; b=sNGHeXyYAl6gXM88RJcJHf7nmnTK1RKqIF/wbBPN9G 2RjwQVNn84fX3TXlXpuWVK864/gmvVPZf8AcExZMG271yXzvAzRXbOALZWQIWSmY s5xuomNvwRKeQt3ydW4lEHj+gDLHq5eDTYvxxfzPcB8d5Z3cHewLBDIAzk0dDOae c= 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=fm1; bh=ipFoRn hBPTvfnKLtvi231+jsT+4CiCHwWwl5ipxlZDM=; b=DlMhAmgOAOTTm+mG5sEIB7 XXOek8J+2bYBUlHHXT3P+6xzpzr5dHsFDv1md65m4XgEZJhVsEBExYrJmkqDPFgd 56bix5e78+grmBMtY+4/zkedUTRblbJaCFUcdsA0zVxkAd5TWTENnD1aH6vo6NH3 jgcwWKH0sXZffiJkibKC3bmELPhMVYxDTqdHV0vjrRWTdsoNV/Twn6H5PzoHN+4q qIfwT7jMZ6LlL/ZKrk0u7cMBf1LdcjLelRtjel9SZX6U8GX6ZjuOG+FxUEiikcrx 6GShVS9RMCVuW+JOKo/muJz0BZ+2IGzY4wkVUJqF8u+BXYERUdU/OGOp6zd1eetQ == 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 B817324751; Tue, 16 Jan 2018 12:36:19 -0500 (EST) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org, Wei Zhao , john.mcnamara@intel.com Date: Tue, 16 Jan 2018 18:35:48 +0100 Message-ID: <16502434.7BYZQfAC5h@xps> In-Reply-To: <8fc87616-d586-f09a-4c5d-de0b8e610376@intel.com> References: <20171221035200.22479-1-wei.zhao1@intel.com> <24e142fc-e616-14e0-3fc0-608c8834c4c3@intel.com> <8fc87616-d586-f09a-4c5d-de0b8e610376@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: add queue region feature info to release notes 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: Tue, 16 Jan 2018 17:36:20 -0000 16/01/2018 17:01, Ferruh Yigit: > On 1/16/2018 11:49 AM, Ferruh Yigit wrote: > > On 1/16/2018 11:27 AM, Thomas Monjalon wrote: > >> 21/12/2017 19:10, Ferruh Yigit: > >>> On 12/20/2017 7:52 PM, Wei Zhao wrote: > >>>> This patch add inforation about i40e queue region > >>>> realted to release notes, it has been missed before. > >>>> > >>>> Signed-off-by: Wei Zhao > >>>> --- > >>>> doc/guides/rel_notes/release_17_11.rst | 17 +++++++++++++++++ > >>> > >>> I think we shouldn't update release notes once it has been released. > >>> > >>> Perhaps it can be an option to mention from this in latest release notes with a > >>> note that says actual support added in v17.11? > >> > >> I disagree. > >> It is really confusing to add 17.11 feature in 18.02 release notes. > >> It is better to add it in 17.11 release notes and backport it. > >> > >> Please Ferruh, could you remove the patch v2 updating release_18_02.rst > >> from next-net? > > > > Updating a release notes after release looks wrong to me. But I will update the > > repo to move this into 17.11 release notes, no patch required. > > > > And there is one more similar update, I guess that should be updated too, I will > > check it as well. > > Other one is following: > https://dpdk.org/dev/patchwork/patch/33283/ > > Updated those two commits to edit v17.11 release notes instead of v18.02. Thanks