From mboxrd@z Thu Jan 1 00:00:00 1970 From: Remy Horton Subject: Re: [PATCH v4 5/5] ethtool: dispaly firmware version Date: Fri, 6 Jan 2017 15:55:06 +0000 Message-ID: References: <1482841816-54143-1-git-send-email-qiming.yang@intel.com> <1483531428-14481-1-git-send-email-qiming.yang@intel.com> <1483531428-14481-6-git-send-email-qiming.yang@intel.com> <416747ed-2df3-10d9-5f01-39e77c84b66b@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "Zhang, Helin" To: "Yang, Qiming" , "Yigit, Ferruh" , "dev@dpdk.org" Return-path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id CB7BA2A58 for ; Fri, 6 Jan 2017 16:55:10 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 05/01/2017 01:31, Yang, Qiming wrote: [..] >> + if (strcmp(drvinfo->driver, "net_ixgbe") == 0) > > Do you need this check. I think it is not good idea to add this kind > of checks into ethtool app. Why not just print "%d.%d.%d %#X, major, > minor, patch, etrack" for all cases ? > Qiming: because I want to keep the format same with kernel version ethtool. My feeling is that if we're going to have driver-specific output, then the task of constructing the string should be pushed down into the PMDs. It would also solve the headache of trying to standardise, as Thomas has mentioned.. ..Remy