From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fengnan Chang <changfengnan@bytedance.com>
Subject: |WARNING| pw127162 [PATCH v2] eal: fix eal init may failed when too much continuous memsegs under legacy mode
Date: Mon, 22 May 2023 14:41:53 +0200 (CEST) [thread overview]
Message-ID: <20230522124153.968C5120927@dpdk.org> (raw)
In-Reply-To: <20230522124107.99877-1-changfengnan@bytedance.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/127162
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:TYPO_SPELLING: 'argment' may be misspelled - perhaps 'argument'?
#87:
Fix this by add a argment indicate how many pages mapped in
WARNING:TYPO_SPELLING: 'Couldn' may be misspelled - perhaps 'Could'?
#110:
EAL: Couldn't remap hugepage files into memseg lists
total: 0 errors, 2 warnings, 87 lines checked
next parent reply other threads:[~2023-05-22 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230522124107.99877-1-changfengnan@bytedance.com>
2023-05-22 12:41 ` checkpatch [this message]
2023-05-22 15:40 ` |FAILURE| " 0-day Robot
2023-05-23 11:19 ` |SUCCESS| " qemudev
2023-05-23 11:20 ` |FAILURE| " qemudev
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=20230522124153.968C5120927@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).