From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 1017) id A95E44C8F; Fri, 8 Mar 2019 06:41:17 +0100 (CET) In-Reply-To: <20190308053859.19980-1-jerry.lilijun@huawei.com> References: <20190308053859.19980-1-jerry.lilijun@huawei.com> To: test-report@dpdk.org Cc: Lilijun Message-Id: <20190308054117.A95E44C8F@dpdk.org> Date: Fri, 8 Mar 2019 06:41:17 +0100 (CET) From: checkpatch@dpdk.org Subject: [dpdk-test-report] |WARNING| pw50978 [PATCH] eal: unmap unneed dpdk VA spaces for legacy mem 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: Fri, 08 Mar 2019 05:41:17 -0000 Test-Label: checkpatch Test-Status: WARNING http://dpdk.org/patch/50978 _coding style issues_ WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #17: Comparing dpdk VA spaces to dpdk 16.11, the dpdk app process's VA spaces increase to above 30G. WARNING:LONG_LINE: line over 90 characters #40: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:1635: + void *va = (void*)((char*)msl->base_va + idx * msl->page_sz); ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)" #40: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:1635: + void *va = (void*)((char*)msl->base_va + idx * msl->page_sz); ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)" #40: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:1635: + void *va = (void*)((char*)msl->base_va + idx * msl->page_sz); total: 2 errors, 2 warnings, 20 lines checked