From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fengnan Chang <changfengnan@bytedance.com>
Subject: |WARNING| pw140342 [PATCH] eal: speed up dpdk init time
Date: Tue, 28 May 2024 08:14:58 +0200 (CEST) [thread overview]
Message-ID: <20240528061458.7401B12367B@dpdk.org> (raw)
In-Reply-To: <20240528061259.29528-1-changfengnan@bytedance.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140342
_coding style issues_
WARNING:TYPO_SPELLING: 'orderd' may be misspelled - perhaps 'ordered'?
#86:
/proc/self/numa_maps is orderd, we can sort hugepg_tbl by orig_va
WARNING:TYPO_SPELLING: 'shoudn' may be misspelled - perhaps 'shouldn'?
#208: FILE: lib/eal/linux/eal_memory.c:489:
+ "shoudn't happen %p", hugepg_tbl[i].orig_va);
total: 0 errors, 2 warnings, 145 lines checked
next prev parent reply other threads:[~2024-05-28 6:14 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528061259.29528-1-changfengnan@bytedance.com>
2024-05-28 5:48 ` |SUCCESS| " qemudev
2024-05-28 5:52 ` qemudev
2024-05-28 6:14 ` checkpatch [this message]
2024-05-28 7:03 ` 0-day Robot
2024-05-28 7:29 ` dpdklab
2024-05-28 7:31 ` dpdklab
2024-05-28 7:36 ` dpdklab
2024-05-28 7:36 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:37 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:38 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:39 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:40 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:41 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:42 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:43 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:44 ` dpdklab
2024-05-28 7:45 ` dpdklab
2024-05-28 7:45 ` dpdklab
2024-05-28 7:48 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:49 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:50 ` dpdklab
2024-05-28 7:51 ` dpdklab
2024-05-28 7:52 ` dpdklab
2024-05-28 7:52 ` dpdklab
2024-05-28 7:53 ` dpdklab
2024-05-28 7:53 ` dpdklab
2024-05-28 7:54 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:55 ` dpdklab
2024-05-28 7:56 ` dpdklab
2024-05-28 7:56 ` dpdklab
2024-05-28 7:57 ` dpdklab
2024-05-28 7:58 ` dpdklab
2024-05-28 7:58 ` dpdklab
2024-05-28 8:00 ` dpdklab
2024-05-28 8:02 ` dpdklab
2024-05-28 8:33 ` dpdklab
2024-05-28 8:34 ` dpdklab
2024-05-28 8:55 ` dpdklab
2024-05-28 8:56 ` dpdklab
2024-05-28 8:57 ` dpdklab
2024-05-28 8:58 ` dpdklab
2024-05-28 9:01 ` dpdklab
2024-05-28 9:01 ` dpdklab
2024-05-28 9:03 ` dpdklab
2024-05-28 9:08 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-30 1:01 ` dpdklab
2024-05-30 1:01 ` dpdklab
2024-05-30 1:03 ` 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=20240528061458.7401B12367B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=changfengnan@bytedance.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).