automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gregory Etelson <getelson@nvidia.com>
Subject: |WARNING| pw152268 [PATCH] rust: support DPDK API
Date: Thu,  6 Mar 2025 14:38:33 +0100 (CET)	[thread overview]
Message-ID: <20250306133833.CC9A31278BF@dpdk.org> (raw)
In-Reply-To: <20250306133713.393057-1-getelson@nvidia.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152268

_coding style issues_


WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#134: 
- bindgen-cli crate

WARNING:TYPO_SPELLING: 'coversion' may be misspelled - perhaps 'conversion'?
#181: FILE: buildtools/rust-env.sh:6:
+# The coversion is done in 4 stages:

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#297: FILE: examples/rust/helloworld/build.rs:4:
+    let mut pkgconfig = Command::new("pkg-config");

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#397: FILE: examples/rust/helloworld/src/main.rs:77:
+    let mut port_id:DpdkPort = 0 as DpdkPort;

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#417: FILE: examples/rust/helloworld/src/main.rs:97:
+pub unsafe fn init_port_config(port: &mut Port) {

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#419: FILE: examples/rust/helloworld/src/main.rs:99:
+        rte_eth_dev_info_get(port.port_id, &mut port.dev_info as *mut rte_eth_dev_info)

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#419: FILE: examples/rust/helloworld/src/main.rs:99:
+        rte_eth_dev_info_get(port.port_id, &mut port.dev_info as *mut rte_eth_dev_info)

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#425: FILE: examples/rust/helloworld/src/main.rs:105:
+    port.dev_conf.rx_adv_conf.rss_conf.rss_key = std::ptr::null_mut();

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#437: FILE: examples/rust/helloworld/src/main.rs:117:
+    let mut name_buf:[c_char;RTE_ETH_NAME_MAX_LEN as usize]= [0 as c_char;RTE_ETH_NAME_MAX_LEN as usize];

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#441: FILE: examples/rust/helloworld/src/main.rs:121:
+        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'?
#450: FILE: examples/rust/helloworld/src/main.rs:130:
+unsafe fn start_port(port:&mut Port) {

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#451: FILE: examples/rust/helloworld/src/main.rs:131:
+    let mut rc = unsafe {

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#465: FILE: examples/rust/helloworld/src/main.rs:145:
+    let mbuf_pool : *mut dpdklib::rte_mbuf::rte_mempool = unsafe {

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#469: FILE: examples/rust/helloworld/src/main.rs:149:
+    if mbuf_pool  == 0 as *mut dpdklib::rte_mbuf::rte_mempool {

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#474: FILE: examples/rust/helloworld/src/main.rs:154:
+    let mut rxq_conf:rte_eth_rxconf = port.dev_info.default_rxconf.clone();

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#478: FILE: examples/rust/helloworld/src/main.rs:158:
+                               &mut rxq_conf as *mut rte_eth_rxconf,

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#478: FILE: examples/rust/helloworld/src/main.rs:158:
+                               &mut rxq_conf as *mut rte_eth_rxconf,

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#479: FILE: examples/rust/helloworld/src/main.rs:159:
+                               mbuf_pool as *mut dpdklib::rte_ethdev::rte_mempool)

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#492: FILE: examples/rust/helloworld/src/main.rs:172:
+    let mut argv: Vec<*mut c_char> = env::args()

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#492: FILE: examples/rust/helloworld/src/main.rs:172:
+    let mut argv: Vec<*mut c_char> = env::args()

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#496: FILE: examples/rust/helloworld/src/main.rs:176:
+        rte_eal_init(env::args().len() as c_int, argv.as_mut_ptr())

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#502: FILE: examples/rust/helloworld/src/main.rs:182:
+    let mut ports:Vec<Port> = vec![];

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#506: FILE: examples/rust/helloworld/src/main.rs:186:
+            let mut port = Port::new(port_id);

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#507: FILE: examples/rust/helloworld/src/main.rs:187:
+            init_port_config(&mut port);

WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#509: FILE: examples/rust/helloworld/src/main.rs:189:
+            start_port(&mut port);

total: 0 errors, 25 warnings, 329 lines checked

  parent reply	other threads:[~2025-03-06 13:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250306133713.393057-1-getelson@nvidia.com>
2025-03-06 13:03 ` |SUCCESS| " qemudev
2025-03-06 13:07 ` qemudev
2025-03-06 13:38 ` checkpatch [this message]
2025-03-06 14:44 ` 0-day Robot
2025-03-06 15:28 ` dpdklab
2025-03-06 15:43 ` dpdklab
2025-03-06 15:52 ` dpdklab
2025-03-06 15:55 ` dpdklab
2025-03-06 16:04 ` dpdklab
2025-03-06 16:09 ` |PENDING| " dpdklab
2025-03-06 16:11 ` dpdklab
2025-03-06 16:18 ` |SUCCESS| " dpdklab
2025-03-06 16:19 ` |PENDING| " dpdklab
2025-03-06 16:34 ` |SUCCESS| " dpdklab
2025-03-06 16:41 ` dpdklab
2025-03-06 16:52 ` |PENDING| " dpdklab
2025-03-06 16:55 ` dpdklab
2025-03-06 17:34 ` |SUCCESS| " dpdklab
2025-03-06 17:48 ` dpdklab
2025-03-06 18:19 ` dpdklab
2025-03-06 18:25 ` 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=20250306133833.CC9A31278BF@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).