From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Linhaifeng <haifeng.lin@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw66526 [PATCH v5] eal/arm64: fix rdtsc precise version
Date: Wed, 11 Mar 2020 04:41:35 +0100 (CET) [thread overview]
Message-ID: <20200311034135.A6CCC1BFFE@dpdk.org> (raw)
In-Reply-To: <4099DE2E54AFAD489356C6C9161D53339729F961@DGGEML502-MBX.china.huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/66526
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#60:
From 70acca49c2109ef07e522229dd035c5b66d7987d Mon Sep 17 00:00:00 2001
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#89: FILE: lib/librte_eal/common/include/arch/arm/rte_cycles_64.h:62:
+#define isb() asm volatile("isb" : : : "memory")
total: 2 errors, 0 warnings, 31 lines checked
next parent reply other threads:[~2020-03-11 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4099DE2E54AFAD489356C6C9161D53339729F961@DGGEML502-MBX.china.huawei.com>
2020-03-11 3:41 ` checkpatch [this message]
2020-03-11 5:04 ` [dpdk-test-report] |SUCCESS| pw66526 devtools: add acronyms in dictionary for commit checks 0-day Robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200311034135.A6CCC1BFFE@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=haifeng.lin@huawei.com \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).