From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 00/20] DPDK PMD for ThunderX NIC device Date: Wed, 08 Jun 2016 15:42:14 +0200 Message-ID: <28207692.5xZGMHagFl@xps13> References: <1464540424-12631-1-git-send-email-jerin.jacob@caviumnetworks.com> <57580FE4.3060808@intel.com> <20160608124319.GA4449@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Ferruh Yigit , dev@dpdk.org, bruce.richardson@intel.com To: Jerin Jacob Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 386F95A53 for ; Wed, 8 Jun 2016 15:42:16 +0200 (CEST) Received: by mail-wm0-f49.google.com with SMTP id k204so17772313wmk.0 for ; Wed, 08 Jun 2016 06:42:16 -0700 (PDT) In-Reply-To: <20160608124319.GA4449@localhost.localdomain> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-06-08 18:13, Jerin Jacob: > On Wed, Jun 08, 2016 at 01:30:28PM +0100, Ferruh Yigit wrote: > > Hi Jerin, > > > > In patch subject, as tag, other drivers are using only driver name, and > > Intel drivers also has "driver/base", since base code has some special > > case. For thunderx, what do you think about keeping subject as: > > "thunderx: ...." > > > > Hi Ferruh, > > We may add crypto or other builtin ThunderX HW accelerated block drivers > in future to DPDK. > So that is the reason why I thought of keeping the subject as thunderx/nicvf. > If you don't have any objection then I would like to keep it as > thunderx/nicvf or just nicvf. I don't like the name nicvf but I guess that's the official name? Thus I agree the title should be thunderx/nicvf or thunderx_nicvf.