From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 1017) id C4C051B3BF; Tue, 7 Nov 2017 23:30:23 +0100 (CET) In-Reply-To: <20171107222913.65295-1-ferruh.yigit@intel.com> References: <20171107222913.65295-1-ferruh.yigit@intel.com> To: test-report@dpdk.org Cc: Ferruh Yigit Message-Id: <20171107223023.C4C051B3BF@dpdk.org> Date: Tue, 7 Nov 2017 23:30:23 +0100 (CET) From: checkpatch@dpdk.org Subject: [dpdk-test-report] |WARNING| pw31254 [PATCH v2] igb_uio: remove device reset in release 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: , X-List-Received-Date: Tue, 07 Nov 2017 22:30:23 -0000 Test-Label: checkpatch Test-Status: WARNING http://dpdk.org/patch/31254 _coding style issues_ ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("")' - ie: 'commit 0123456789ab ("commit description")' #28: This is close to reverting commit b58eedfc7dd5 [2], taking into account ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")' #44: Still igb_uio should be safer comparing to the pre b58eedfc7dd5 state. ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")' #50: b58eedfc7dd5 ("igb_uio: issue FLR during open and release of device file") ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")' #53: f73b38e9245d ("igb_uio: remove device reset in open") total: 4 errors, 0 warnings, 23 lines checked