From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Wangyu (Turing Solution Development Dep)" <seven.wangyu@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw62356 [PATCH] bus/pci: resolve multiple NICs address conflicts
Date: Mon, 4 Nov 2019 12:04:40 +0100 (CET) [thread overview]
Message-ID: <20191104110440.4F99B4C93@dpdk.org> (raw)
In-Reply-To: <78A93308629D474AA53B84C5879E84D24B0FF99F@DGGEMM533-MBX.china.huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/62356
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#63:
NIC address conflicts on 64K pagesize when using multiple NICs, as system will mmap 64K pagesize for NIC, but dev->mem_resource[i].len is 16K.
WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Wangyu (Turing Solution Development Dep) <seven.wangyu@huawei.com>'
total: 0 errors, 2 warnings, 11 lines checked
prev parent reply other threads:[~2019-11-04 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <78A93308629D474AA53B84C5879E84D24B0FF99F@DGGEMM533-MBX.china.huawei.com>
2019-11-04 10:04 ` [dpdk-test-report] |SUCCESS| pw62356 " 0-day Robot
2019-11-04 11:04 ` checkpatch [this message]
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=20191104110440.4F99B4C93@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=seven.wangyu@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).