From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 1/2] ethdev: add supported hash function check Date: Wed, 18 Apr 2018 14:15:04 +0200 Message-ID: <6024675.SqA4AgUrAM@xps> References: <20180409121035.148813-1-xuemingl@mellanox.com> <38100809.DTC8XynbX7@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "dev@dpdk.org" , Shahaf Shuler , Nelio Laranjeiro , Wenzhuo Lu , Jingjing Wu To: "Xueming(Steven) Li" Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id B4E808D90 for ; Wed, 18 Apr 2018 14:15:07 +0200 (CEST) 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" 18/04/2018 13:55, Xueming(Steven) Li: > From: Thomas Monjalon > > 17/04/2018 16:24, Xueming Li: > > > + /* Check that device supports requested rss hash functions. */ > > > + if ((dev_info.flow_type_rss_offloads | > > > + dev_conf->rx_adv_conf.rss_conf.rss_hf) != > > > + dev_info.flow_type_rss_offloads) { > > > + RTE_PMD_DEBUG_TRACE("ethdev port_id=%d invalid rss_hf: 0x%lx, valid value: 0x%lx\n", > > > + port_id, > > > + dev_conf->rx_adv_conf.rss_conf.rss_hf, > > > + dev_info.flow_type_rss_offloads); > > > + return -EINVAL; > > > + } > > > > Please use PRIx64 and test 32-bit compilation. > > > > Reminder from this recent post: > > > > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk.org%2Fml%2Farchives%2Fdev%2F201 > > 8- > > February%2F090882.html&data=02%7C01%7Cxuemingl%40mellanox.com%7C5508bc716aac41b932fb08d5a4aeb241%7Ca65 > > 2971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636595992591300475&sdata=1hirZ1j7VqCMnrzngZFAuQj42OACfxFUgYgzy > > VQyw%2F4%3D&reserved=0 > > " > > Most of the times, using %l is wrong (except when printing a long). > > So next time you write %l, please think "I am probably wrong". > > " > > Thanks, got following warning from checkpatch when applying this rule to my other patchset, is it normal? > CHECK:CAMELCASE: Avoid CamelCase: > #49: FILE: drivers/net/mlx5/mlx5_flow.c:2083: > + " hash:%" PRIx64 "/%u specs:%hhu(%hu), priority:%hu, type:%d," > Yes it is "normal". Something we should fix in checkpatch.