From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>
Subject: |WARNING| pw153041 [PATCH 3/3] rust: showcase port Rxq return for stop and reconfigure
Date: Fri, 18 Apr 2025 15:24:18 +0200 (CEST) [thread overview]
Message-ID: <20250418132418.8B063123FA7@dpdk.org> (raw)
In-Reply-To: <20250418132324.4085336-3-harry.van.haaren@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153041
_coding style issues_
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#109: FILE: rust_api_example/examples/eth_poll.rs:32:
+ let mut rxq2 = rxq2.enable_polling();
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#111: FILE: rust_api_example/examples/eth_poll.rs:34:
+ let _nb_mbufs = rxq2.rx_burst(&mut [0; 32]);
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#165: FILE: rust_api_example/src/lib.rs:15:
+ pub(crate) struct PortHandle(Arc<()>);
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#171: FILE: rust_api_example/src/lib.rs:21:
+ fn stop(&mut self) -> Result<(), usize> {
ERROR:TRAILING_WHITESPACE: trailing whitespace
#184: FILE: rust_api_example/src/lib.rs:34:
+ $
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#199: FILE: rust_api_example/src/lib.rs:47:
+ pub(crate) fn new(handle: PortHandle, port: u16, queue: u16) -> Self {
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#241: FILE: rust_api_example/src/lib.rs:135:
+ pub fn stop(&mut self) -> Result<(), String> {
total: 1 errors, 6 warnings, 158 lines checked
prev parent reply other threads:[~2025-04-18 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250418132324.4085336-3-harry.van.haaren@intel.com>
2025-04-18 12:49 ` |SUCCESS| pw153039-153041 [PATCH 3/3] rust: showcase port Rxq return for stop() " qemudev
2025-04-18 12:53 ` qemudev
2025-04-18 13:24 ` 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=20250418132418.8B063123FA7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=harry.van.haaren@intel.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).