From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Lilijun (Jerry)" <jerry.lilijun@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw69355 [PATCH] lib/librte_hash: add rte_hash_del_key_fixed without compact
Date: Mon, 27 Apr 2020 04:29:53 +0200 (CEST) [thread overview]
Message-ID: <20200427022953.3CF2D1C127@dpdk.org> (raw)
In-Reply-To: <40280F65B1B0B44E8089ED31C01616EBA49921F2@dggeml529-mbx.china.huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/69355
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#58:
The keys idx are stored in rte_hash main bucket key slots and extend bucket key stots.
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 1 warnings, 67 lines checked
ERROR: symbol rte_hash_del_key_fixed is added in the DPDK_20.0 section, but is expected to be added in the EXPERIMENTAL section of the version map
next parent reply other threads:[~2020-04-27 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40280F65B1B0B44E8089ED31C01616EBA49921F2@dggeml529-mbx.china.huawei.com>
2020-04-27 2:29 ` checkpatch [this message]
2020-04-27 6:13 ` [dpdk-test-report] || pw69355 " 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=20200427022953.3CF2D1C127@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jerry.lilijun@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).