From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5CDF4A0548; Mon, 26 Apr 2021 15:51:34 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 24BF741110; Mon, 26 Apr 2021 15:51:34 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by mails.dpdk.org (Postfix) with ESMTP id B517141104; Mon, 26 Apr 2021 15:51:32 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.nyi.internal (Postfix) with ESMTP id 207ED5803A6; Mon, 26 Apr 2021 09:51:32 -0400 (EDT) Received: from imap4 ([10.202.2.54]) by compute2.internal (MEProxy); Mon, 26 Apr 2021 09:51:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type:content-transfer-encoding; s=fm1; bh=K2PyZ OYYki48zL8LyoK8It4A5g1FkBi+JMOn0cXouZo=; b=Q6CoFeDHkS2bPx0/EdX48 V/pw4A2nHpBt9Vpk8rCrEfTg2aSFtGcMiCtUBXwwX7jjFuc5VYyORKun3pv4/8zQ slm3JURX2zPDLBut/Pl53HETwKnzxIn+RnK1MbA+iuXus7h6WDTeZKLDkDOEPu8A kxzqrt/SB+o+MKewhOePLF4QhLGFCDHGkhSNln7sWdQyZNuoPdg5x/eZok9Tb4cf bkWMaRGS/+GUllx9+JSHpx2bSqN8IDrHLvJpDcfFPnhriielResKN8qTGfkaVxxh 31EKOnH+oWQioyr3+vhtcq/qAMUu1V+BEKsXM6zly1QnqMOdOluiV/QqiaySKJlk A== 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=K2PyZOYYki48zL8LyoK8It4A5g1FkBi+JMOn0cXou Zo=; b=V8rHh+/AuuRLahA2Bh0VfUug9PYYcxwsvR6ydwFPmrQmxe5zmhz3z+F5T tr61Z6SMT/fFKwXlcnIOWTAbTNoN2ePXLWW55hAEeK2Lw6FW+t2acivLV5Vusjcl CH11nYIb1aE1epbFNZNqVH8UF1TaQqFWueP4LwAt6JtB7IHGY7r60xNTtaE8/gtT W4SP0gN1U3f0KzV3iHrM4oGoa278fiCTpuXFNB89WO7lAVntZoU82TGzyHD52bOG EyGz5i1VHSL3366tI8ksXHM7pNjH6Y2v6BhyJPui2kFV6bqcgoKZ6cOZN9+qTJMS bbngyyrwXn1GEn9H/pL2icW+PtzlQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddukedgjeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfvfhh ohhmrghsucfoohhnjhgrlhhonhdfuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvth eqnecuggftrfgrthhtvghrnhepvefhgeekuddtkedvvddujeeufeduudelteehkefhvdeh geetleffteekjeelieetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id B17C7160686; Mon, 26 Apr 2021 09:51:31 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-403-gbc3c488b23-fm-20210419.005-gbc3c488b Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20210225114622.2431-1-heinrich.kuhn@netronome.com> <54de2177-d56c-2281-2e92-8603450a99c6@intel.com> <92790507-cabd-ba37-2016-9b5c48c2416f@intel.com> Date: Mon, 26 Apr 2021 15:51:09 +0200 From: "Thomas Monjalon" To: "Ferruh Yigit" , "David Marchand" , "gakhil@marvell.com" , "Jerin Jacob Kollanukkaran" , "Maxime Coquelin" , "Qi Zhang" , "Raslan Darawsheh" , "Ajit Khaparde" Cc: dev@dpdk.org, "Heinrich Kuhn" , "techboard@dpdk.org" Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: fix nfp multiport syntax X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Lun 26 avr 2021, =C3=A0 11:48, Ferruh Yigit a =C3=A9crit=E2=80=AF: > Hi Thomas, David, Akhil, Jerin, Maxime, Qi, Raslan, Ajit, >=20 > For the doc patches, the subsystem prefix 'doc:' is too wide, what do = you think=20 > to extend it to include the component, like for this patch: > "doc/nics/nfp: fix multiport syntax" Usually I format like this: doc: fix multiport syntax in nfp guide I am not sure about being precise in the doc prefix for 2 reasons: - the doc hierarchy can be quite complex - it may give too much importance visually to the doc changes But if everybody prefer a precise prefix, I am OK to change the habit.