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 CF6D92BF7 for ; Thu, 23 Aug 2018 13:35:19 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 458E821161; Thu, 23 Aug 2018 07:35:19 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 23 Aug 2018 07:35:19 -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=FPKPmwQq+cpdP+S1w0dBzmFnuj L17SB4CST15yk1+TI=; b=ozpLR1A/Y/b2ltwtG0hYCdGEo3lF2s2C9+jl4O9gd+ f0yNLZYeopvlurQaLJ2NVIckrPsVoMLiuAuTpSA5ePH8X5atDJs7igKpT9CFRX9P mH+mk25MCrloxFbMvyXhn4Yk6Ua5OkfUzNMWvy9qHATrnIsz3Vipl188DOfQn8vn 8= 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=fm3; bh=FPKPmw Qq+cpdP+S1w0dBzmFnujL17SB4CST15yk1+TI=; b=jW66cDlz08PGEPWb5yFF/H NeqFL3RhWtI8TfwRVCc+Yuox5sjxldz3AZ7HlfHwqE+jjbix0va4XJRROL3Ylg6u XGp5Kr+Dxh56J2IxOL0Mq9n3hs0vwcbEsXKOgQY8rGmvVl9bt+qwdf0UmL9juc9Q 6V/RSbgpRshGNEsfidCUTz+xxbC2cQeMwA0pjDEEebJBRcjRCAdV/e9CcjLp3vvC HCXbq1jVJ3UqCW8ahByzgY+d7QDucLS7Bq7nqjtKoQitB+WGgs69BvCcmGcIYee7 uyxPAhzw8EVdUn40ZS+Kj3v8bL4YRaOR9IeiH2c3fQdnF3/ZWE+/jMuy3UcRt09w == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (163.41.136.77.rev.sfr.net [77.136.41.163]) by mail.messagingengine.com (Postfix) with ESMTPA id 1B7A8E4693; Thu, 23 Aug 2018 07:35:16 -0400 (EDT) From: Thomas Monjalon To: Akhil Goyal Cc: Fiona Trahe , dev@dpdk.org, pablo.de.lara.guarch@intel.com, tomaszx.jozwiak@intel.com Date: Thu, 23 Aug 2018 13:35:14 +0200 Message-ID: <4241237.uuHHh3i2W6@xps> In-Reply-To: <139db8d3-9ece-9112-9fcd-208f5130c904@nxp.com> References: <1533833430-29134-8-git-send-email-fiona.trahe@intel.com> <2703345.FnO9srYX5e@xps> <139db8d3-9ece-9112-9fcd-208f5130c904@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 0/6] doc/qat: clarify build config options 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: Thu, 23 Aug 2018 11:35:20 -0000 23/08/2018 13:28, Akhil Goyal: > Hi Thomas, > > On 8/23/2018 4:54 PM, Thomas Monjalon wrote: > > > 23/08/2018 13:12, Akhil Goyal: > >> Patchset applied to dpdk-next-crypto. > >> > >> Subject for "doc/qat: fix typos and make cosmetic changes" changed to "doc/qat: correct typo and make cosmetic changes" > >> > >> to avoid git log error. > > Which error? Lack of Fixes tag? > > As a committer, you must be sure the Fixes tags and Cc: stable@dpdk.org > > are all set. It is mandatory to know what should be backported and where. > > Even typos should be backported. > > > > > Fiona clarified that this patch is not required for back porting. It will make future backporting of doc fixes harder. That's a good example to discuss. OK to keep it as is, and will discuss it with maintainers of stable branches during the Dublin event, in order to make the policies clear.