From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 67C45A052F for ; Sun, 26 Jan 2020 18:26:36 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 557441B53; Sun, 26 Jan 2020 18:26:36 +0100 (CET) Received: by dpdk.org (Postfix, from userid 1017) id CBAEB4C7A; Sun, 26 Jan 2020 18:26:34 +0100 (CET) In-Reply-To: <20200126172548.23327-1-dharton@cisco.com> References: <20200126172548.23327-1-dharton@cisco.com> To: test-report@dpdk.org Cc: David Harton Message-Id: <20200126172634.CBAEB4C7A@dpdk.org> Date: Sun, 26 Jan 2020 18:26:34 +0100 (CET) From: checkpatch@dpdk.org Subject: [dpdk-test-report] |WARNING| pw65131 [PATCH v2] net/e1000: update UPDATE_VF_STAT to handle rollover X-BeenThere: test-report@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: automatic DPDK test reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: test-report-bounces@dpdk.org Sender: "test-report" Test-Label: checkpatch Test-Status: WARNING http://dpdk.org/patch/65131 _coding style issues_ ERROR:BAD_SIGN_OFF: Unrecognized email address: 'intel.com' #69: Cc: intel.com CHECK:MACRO_ARG_REUSE: Macro argument reuse 'last' - possible side-effects? #89: FILE: drivers/net/e1000/igb_ethdev.c:264: +#define UPDATE_VF_STAT(reg, last, cur) \ +{ \ + u32 latest = E1000_READ_REG(hw, reg); \ + if (latest >= last) \ + cur += (latest - last); \ + else \ + cur += ((latest + ((uint64_t)1 << 32)) - last); \ + cur &= UINT_MAX; \ + last = latest; \ } CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'last' may be better as '(last)' to avoid precedence issues #89: FILE: drivers/net/e1000/igb_ethdev.c:264: +#define UPDATE_VF_STAT(reg, last, cur) \ +{ \ + u32 latest = E1000_READ_REG(hw, reg); \ + if (latest >= last) \ + cur += (latest - last); \ + else \ + cur += ((latest + ((uint64_t)1 << 32)) - last); \ + cur &= UINT_MAX; \ + last = latest; \ } CHECK:MACRO_ARG_REUSE: Macro argument reuse 'cur' - possible side-effects? #89: FILE: drivers/net/e1000/igb_ethdev.c:264: +#define UPDATE_VF_STAT(reg, last, cur) \ +{ \ + u32 latest = E1000_READ_REG(hw, reg); \ + if (latest >= last) \ + cur += (latest - last); \ + else \ + cur += ((latest + ((uint64_t)1 << 32)) - last); \ + cur &= UINT_MAX; \ + last = latest; \ } CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'cur' may be better as '(cur)' to avoid precedence issues #89: FILE: drivers/net/e1000/igb_ethdev.c:264: +#define UPDATE_VF_STAT(reg, last, cur) \ +{ \ + u32 latest = E1000_READ_REG(hw, reg); \ + if (latest >= last) \ + cur += (latest - last); \ + else \ + cur += ((latest + ((uint64_t)1 << 32)) - last); \ + cur &= UINT_MAX; \ + last = latest; \ } total: 1 errors, 0 warnings, 4 checks, 20 lines checked