From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Wei Hu (Xavier)" <huwei013@chinasoftinc.com>
Subject: [dpdk-test-report] |WARNING| pw79178 [PATCH 2/9] net/hns3: maximize the queue number
Date: Tue, 29 Sep 2020 13:11:48 +0200 (CEST) [thread overview]
Message-ID: <20200929111148.80D3D1D90B@dpdk.org> (raw)
In-Reply-To: <20200929110945.70761-3-huwei013@chinasoftinc.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/79178
_coding style issues_
WARNING:TYPO_SPELLING: 'drvier' may be misspelled - perhaps 'driver'?
#74:
driver. If maximum queue numbers allocated to PF PMD drvier is less than
WARNING:TYPO_SPELLING: 'maximun' may be misspelled - perhaps 'maximum'?
#82:
keep the maximun 64 queues based on hns3 network engine with revision_id
WARNING:TYPO_SPELLING: 'avarage' may be misspelled - perhaps 'average'?
#107:
are allocated to every TC by avarage. So Rx and Tx queue numbers must be
WARNING:TYPO_SPELLING: 'fpr' may be misspelled - perhaps 'for'?
#527: FILE: drivers/net/hns3/hns3_ethdev.c:2680:
+ * maximum queue number of pf fpr network engine with
total: 0 errors, 4 warnings, 0 checks, 946 lines checked
parent reply other threads:[~2020-09-29 11:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200929110945.70761-3-huwei013@chinasoftinc.com>]
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=20200929111148.80D3D1D90B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=huwei013@chinasoftinc.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).