From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>
Subject: |WARNING| pw153040 [PATCH 2/3] rust: split main into example, refactor to lib.rs
Date: Fri, 18 Apr 2025 15:24:21 +0200 (CEST) [thread overview]
Message-ID: <20250418132421.85482123FAC@dpdk.org> (raw)
In-Reply-To: <20250418132324.4085336-2-harry.van.haaren@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153040
_coding style issues_
WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#91: FILE: rust_api_example/examples/eth_poll.rs:7:
+ let mut dpdk = dpdk::Eal::init().expect("dpdk must init ok");
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#94: FILE: rust_api_example/examples/eth_poll.rs:10:
+ let mut ports = dpdk.take_eth_ports().expect("take eth ports ok");
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#95: FILE: rust_api_example/examples/eth_poll.rs:11:
+ let mut p = ports.pop().unwrap();
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#100: FILE: rust_api_example/examples/eth_poll.rs:16:
+ let (mut rxqs, _txqs) = p.start();
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#107: FILE: rust_api_example/examples/eth_poll.rs:23:
+ let mut rxq = rxq1.enable_polling();
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#109: FILE: rust_api_example/examples/eth_poll.rs:25:
+ let _nb_mbufs = rxq.rx_burst(&mut [0; 32]);
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#114: FILE: rust_api_example/examples/eth_poll.rs:30:
+ let mut rxq = rxq2.enable_polling();
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#116: FILE: rust_api_example/examples/eth_poll.rs:32:
+ let _nb_mbufs = rxq.rx_burst(&mut [0; 32]);
total: 0 errors, 9 warnings, 38 lines checked
parent reply other threads:[~2025-04-18 13:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250418132324.4085336-2-harry.van.haaren@intel.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=20250418132421.85482123FAC@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).