From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gregory Etelson <getelson@nvidia.com>
Subject: |WARNING| pw152423 [PATCH v3] rust: support raw DPDK API
Date: Fri, 14 Mar 2025 19:39:38 +0100 (CET) [thread overview]
Message-ID: <20250314183938.5C63B123FF5@dpdk.org> (raw)
In-Reply-To: <20250314183815.246612-1-getelson@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152423
_coding style issues_
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#123:
RUST API files into raw module under dpdk crate.
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#128:
RUST DPDK application must specify the `dpdk` crate as
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#131:
RUST `dpdk` crate is installed into
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#137:
- bindgen-cli crate
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#142:
$MESON_INSTALL_DESTDIR_PREFIX/$libdir/rust crate.
WARNING:TYPO_SPELLING: 'coversion' may be misspelled - perhaps 'conversion'?
#192: FILE: buildtools/rust-env.sh:6:
+# The coversion is done in 4 stages:
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#267: FILE: buildtools/rust-env.sh:81:
+echo "Install RUST DPDK crate in $rust_dir"
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#290: FILE: examples/rust/helloworld/build.rs:4:
+ let mut pkgconfig = Command::new("pkg-config");
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#386: FILE: examples/rust/helloworld/src/main.rs:70:
+ pub unsafe fn init_port_config(&mut self) {
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#388: FILE: examples/rust/helloworld/src/main.rs:72:
+ rte_eth_dev_info_get(self.port_id, &mut self.dev_info as *mut rte_eth_dev_info)
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#388: FILE: examples/rust/helloworld/src/main.rs:72:
+ rte_eth_dev_info_get(self.port_id, &mut self.dev_info as *mut rte_eth_dev_info)
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#394: FILE: examples/rust/helloworld/src/main.rs:78:
+ self.dev_conf.rx_adv_conf.rss_conf.rss_key = std::ptr::null_mut();
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#407: FILE: examples/rust/helloworld/src/main.rs:91:
+ unsafe fn start_port(&mut self) {
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#408: FILE: examples/rust/helloworld/src/main.rs:92:
+ let mut rc = unsafe {
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#428: FILE: examples/rust/helloworld/src/main.rs:112:
+ let mbuf_pool: *mut dpdk::raw::rte_mbuf::rte_mempool = unsafe {
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#438: FILE: examples/rust/helloworld/src/main.rs:122:
+ if mbuf_pool == 0 as *mut dpdk::raw::rte_mbuf::rte_mempool {
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#443: FILE: examples/rust/helloworld/src/main.rs:127:
+ let mut rxq_conf: rte_eth_rxconf = self.dev_info.default_rxconf.clone();
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#451: FILE: examples/rust/helloworld/src/main.rs:135:
+ &mut rxq_conf as *mut rte_eth_rxconf,
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#451: FILE: examples/rust/helloworld/src/main.rs:135:
+ &mut rxq_conf as *mut rte_eth_rxconf,
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#452: FILE: examples/rust/helloworld/src/main.rs:136:
+ mbuf_pool as *mut dpdk::raw::rte_ethdev::rte_mempool,
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#468: FILE: examples/rust/helloworld/src/main.rs:152:
+ let mut port_id: DpdkPort = 0 as DpdkPort;
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#487: FILE: examples/rust/helloworld/src/main.rs:171:
+ let mut name_buf: [c_char; RTE_ETH_NAME_MAX_LEN as usize] =
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#492: FILE: examples/rust/helloworld/src/main.rs:176:
+ let _rc = rte_eth_dev_get_name_by_port(p.port_id, name_buf.as_mut_ptr());
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#506: FILE: examples/rust/helloworld/src/main.rs:190:
+ let mut argv: Vec<*mut c_char> = env::args()
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#506: FILE: examples/rust/helloworld/src/main.rs:190:
+ let mut argv: Vec<*mut c_char> = env::args()
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#510: FILE: examples/rust/helloworld/src/main.rs:194:
+ let rc = unsafe { rte_eal_init(env::args().len() as c_int, argv.as_mut_ptr()) };
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#517: FILE: examples/rust/helloworld/src/main.rs:201:
+ let mut ports: Vec<Port> = vec![];
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#522: FILE: examples/rust/helloworld/src/main.rs:206:
+ let mut port = Port::new(port_id);
total: 0 errors, 28 warnings, 343 lines checked
next prev parent reply other threads:[~2025-03-14 18:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250314183815.246612-1-getelson@nvidia.com>
2025-03-14 18:05 ` |SUCCESS| " qemudev
2025-03-14 18:09 ` qemudev
2025-03-14 18:39 ` checkpatch [this message]
2025-03-14 19:09 ` |SUCCESS| pw152423 [PATCH] [v3] " dpdklab
2025-03-14 19:20 ` dpdklab
2025-03-14 19:27 ` |PENDING| " dpdklab
2025-03-14 19:27 ` dpdklab
2025-03-14 19:33 ` |SUCCESS| " dpdklab
2025-03-14 19:43 ` dpdklab
2025-03-14 19:48 ` dpdklab
2025-03-14 19:56 ` dpdklab
2025-03-14 20:00 ` dpdklab
2025-03-14 20:02 ` dpdklab
2025-03-14 20:04 ` |PENDING| " dpdklab
2025-03-14 20:22 ` |SUCCESS| " dpdklab
2025-03-14 20:26 ` dpdklab
2025-03-14 20:46 ` |SUCCESS| pw152423 [PATCH v3] " 0-day Robot
2025-03-14 20:49 ` |SUCCESS| pw152423 [PATCH] [v3] " dpdklab
2025-03-14 21:15 ` 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=20250314183938.5C63B123FF5@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=getelson@nvidia.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).