From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 7D5A1D0B2 for ; Mon, 8 Oct 2018 15:37:08 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 18C4F21FF4; Mon, 8 Oct 2018 09:37:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 08 Oct 2018 09:37:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=8WL04/8BsIoKTlrQf9tqreVQDtoy4qKPYM61EOU/ow0=; b=QbF0uNSU4CKE x+W35riCVFkh0nj8wNU2JL5xWphKYdpK3RVcFkPnrjFBmfqDqHJmuJULPaYYB0AL Hi3SYha+mNF3KtyJv/2WZAggUQFXjZvGCXE9aJJouF3rZYewMm4Cwdi8satMI/6t +BCYClf+U/P6zXf3wCQCNhBWl9hxjTE= 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=fm3; bh=8WL04/8BsIoKTlrQf9tqreVQDtoy4qKPYM61EOU/o w0=; b=ZpAHfw5U80IbfPBc7AQj4vV6hcY5Wf5neiQ3c3ApfHVwl8tMxCWYnpbvQ jQJPuG8U1/61ZyASqjUUu0h4eREozNyuyM4QfsXYQ4AcmiaijXtW4pXlo4zMpAse i3AkuCJ6FlxjGGdXHWLXjswfGhHShwiHnXp3PVzxeM6Lz4Nx3/3kZMsriEmsUt1b QlcSOM55MG558/ozsdcn+751liko8whVnkWEOIiSNQqLIT+S5pOp/7B+SAoRAGXn b4hoaqjsztaotdurHFP3rDlDTMCS1HUBfB8Bzcg4AHBerK/sobY5Tm+a1nCarNT+ yIXTKgqh8B4XXZAjvyO15jsjHhZPw== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1061CE4307; Mon, 8 Oct 2018 09:37:05 -0400 (EDT) From: Thomas Monjalon To: "Joseph, Anoob" Cc: dev@dpdk.org, Akhil Goyal , Pablo de Lara , Ankur Dwivedi , Jerin Jacob , Narayana Prasad , Murthy NSSR , Nithin Dabilpuram , Ragothaman Jayaraman , Srisivasubramanian S , Tejasree Kondoj Date: Mon, 08 Oct 2018 15:37:04 +0200 Message-ID: <1640090.FxR765Yp0Y@xps> In-Reply-To: References: <1536033560-21541-1-git-send-email-ajoseph@caviumnetworks.com> <2582518.r5GVpR4kJk@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 01/32] common/cpt: add common logging support 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: Mon, 08 Oct 2018 13:37:08 -0000 08/10/2018 15:07, Joseph, Anoob: > On 08-10-2018 17:57, Thomas Monjalon wrote: > > 05/10/2018 14:58, Anoob Joseph: > >> +Cavium OCTEON TX > >> +M: Anoob Joseph > >> +F: drivers/common/cpt/ > > What is the real wording for this device family? > > Sometimes I read OcteonTX with lowercases and no space, > > sometimes OCTEONTX without space, sometimes OCTEON TX. > > > > Another note: You should differentiate ethdev and cryptodev devices, > > at least in the maintainer file. > > We have nicvf, zipvf, ssovf, timvf. > OCTEON TX (with the space) is the registered name of the chip. nicvf, > zipvf, ssovf, timvf are all multiple blocks on the device and previous > drivers were named that way. CPT is the similar name for the crypto > block. Jerin is planning for a common naming convention for the blocks > on the same family. > > Different blocks would be named crypto_octeontx, event_octeontx etc, to > denote that they are all part of the same device. We had to omit the > space (between OCTEON & TX), since it would complicate the name for the > directories. > > OcteonTX is a wrong convention. It would be fixed going ahead. > > I suggest to add "crypto" to the name of this section. > This entry is already under "Crypto Drivers". So do we need a separate > mention of "crypto"? Yes I think it is better to add "crypto", especially for automated processing of this file, we should avoid to have two times the same section title.