From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: 俞文俊_yewu <yuwenjun_yewu@cmss.chinamobile.com>
Subject: |WARNING| pw106008 [PATCH] net/bonding: fix RSS not work for bonding in DPDK21.11
Date: Tue, 18 Jan 2022 09:50:17 +0100 (CET) [thread overview]
Message-ID: <20220118085017.374EC120923@dpdk.org> (raw)
In-Reply-To: <2afe61e566ebad1-00019.Richmail.00005001707698381847@cmss.chinamobile.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/106008
_coding style issues_
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: bad o ("69d0ce272ae8e8350")'
#59:
From 85c4ffffe32996fc262dd6f69d0ce272ae8e8350 Mon Sep 17 00:00:00 2001
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#64:
RSS don't work when bond_ethdev_configure called before rte_eth_bond_slave_add in DPDK21.11.
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#64:
RSS don't work when bond_ethdev_configure called before rte_eth_bond_slave_add in DPDK21.11.
WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#68:
dont't work(examples/bond/main.c):
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#71:
rte_eth_bond_slave_add()
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#76:
rte_eth_bond_slave_add()
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Yu Wenjun '
#80:
Signed-off-by: Yu Wenjun
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Min Hu (Connor)'
#81:
Acked-by: Min Hu (Connor)
ERROR:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author ''
total: 4 errors, 5 warnings, 0 checks, 11 lines checked
next parent reply other threads:[~2022-01-18 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2afe61e566ebad1-00019.Richmail.00005001707698381847@cmss.chinamobile.com>
2022-01-18 8:50 ` checkpatch [this message]
2022-01-18 17:38 dpdklab
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=20220118085017.374EC120923@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yuwenjun_yewu@cmss.chinamobile.com \
/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).