From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw152832 [RFC PATCH] add rust binding support to DPDK
Date: Tue, 8 Apr 2025 17:00:31 +0200 (CEST) [thread overview]
Message-ID: <20250408150031.1648E123F71@dpdk.org> (raw)
In-Reply-To: <20250408145838.2501034-1-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152832
_coding style issues_
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#71:
be cloned and built as a rust crate - all-be-it one with only two
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#147: FILE: buildtools/rust/build.rs:5:
+extern crate meson_next as meson;
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#169: FILE: buildtools/rust/build.rs:27:
+ let mut bindings = bindgen::Builder::default();
WARNING:TYPO_SPELLING: 'crate' may be misspelled - perhaps 'create'?
#178: FILE: buildtools/rust/build.rs:36:
+ // Tell cargo to invalidate the built crate whenever any of the
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#186: FILE: buildtools/rust/build.rs:44:
+ .expect("Couldn't write bindings!");
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#269: FILE: buildtools/rust/lib.rs:18:
+ let mut argv = [appname.into_raw()];
WARNING:TYPO_SPELLING: 'mut' may be misspelled - perhaps 'must'?
#271: FILE: buildtools/rust/lib.rs:20:
+ rte_eal_init(argv.len().try_into().unwrap(), argv.as_mut_ptr())
total: 0 errors, 7 warnings, 159 lines checked
next prev parent reply other threads:[~2025-04-08 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250408145838.2501034-1-bruce.richardson@intel.com>
2025-04-08 14:25 ` |SUCCESS| " qemudev
2025-04-08 14:30 ` qemudev
2025-04-08 15:00 ` checkpatch [this message]
2025-04-08 16:23 ` |FAILURE| " 0-day Robot
2025-04-08 19:25 ` |FAILURE| pw152832 [PATCH] [RFC] " dpdklab
2025-04-08 19:42 ` 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=20250408150031.1648E123F71@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@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).