automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Linhaifeng <haifeng.lin@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw66502 [PATCH v4] eal/arm64: fix rdtsc precise version
Date: Tue, 10 Mar 2020 11:56:07 +0100 (CET)	[thread overview]
Message-ID: <20200310105607.55D581C00E@dpdk.org> (raw)
In-Reply-To: <4099DE2E54AFAD489356C6C9161D53339729F63A@DGGEML502-MBX.china.huawei.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/66502

_coding style issues_

Must be a reply to the first patch (--in-reply-to).


WARNING:LONG_LINE: line over 90 characters
#117: FILE: lib/librte_eal/common/include/arch/arm/rte_cycles_64.h:64:
+	uint64_t tmp, _val = (val);										\

WARNING:LONG_LINE: line over 90 characters
#118: FILE: lib/librte_eal/common/include/arch/arm/rte_cycles_64.h:65:
+																	\

WARNING:LONG_LINE: line over 90 characters
#119: FILE: lib/librte_eal/common/include/arch/arm/rte_cycles_64.h:66:
+	asm volatile(													\

WARNING:LONG_LINE: line over 90 characters
#123: FILE: lib/librte_eal/common/include/arch/arm/rte_cycles_64.h:70:
+	: "=r" (tmp) : "r" (_val));										\

WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Linhaifeng <haifeng.lin@huawei.com>'

total: 0 errors, 5 warnings, 50 lines checked

       reply	other threads:[~2020-03-10 10:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4099DE2E54AFAD489356C6C9161D53339729F63A@DGGEML502-MBX.china.huawei.com>
2020-03-10 10:56 ` checkpatch [this message]
2020-03-10 19:04 ` [dpdk-test-report] || pw66502 " 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=20200310105607.55D581C00E@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).