From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rahul Gupta <rahulgupt@linux.microsoft.com>
Subject: |WARNING| pw133792 [RFC] eal: RFC to refactor rte_eal_init into sub-functions
Date: Thu, 2 Nov 2023 19:20:46 +0100 (CET) [thread overview]
Message-ID: <20231102182046.187CC120A24@dpdk.org> (raw)
In-Reply-To: <1698949164-20287-1-git-send-email-rahulgupt@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/133792
_coding style issues_
WARNING:TYPO_SPELLING: 'upto' may be misspelled - perhaps 'up to'?
#62:
b) rte_pktmbuf_pool_create() can consume upto 300-350 ms for
WARNING:TYPO_SPELLING: 'appplications' may be misspelled - perhaps 'applications'?
#67:
This patch provides an optimization using pthreads that appplications
ERROR:C99_COMMENTS: do not use C99 // comments
#139: FILE: lib/librte_eal/linux/eal/eal.c:1304:
+ return 0; //return Success if control reaches here
ERROR:SPACING: spaces required around that '>=' (ctx:VxV)
#147: FILE: lib/librte_eal/linux/eal/eal.c:1312:
+ if (fctret>=0)
^
WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatch: 'From: Rahul Gupta <rahulgupt@microsoft.com>' != 'Signed-off-by: Rahul Gupta <rahulgupt@linux.microsoft.com>'
total: 2 errors, 3 warnings, 55 lines checked
ERROR: symbol rte_eal_init_setup is added in the DPDK_20.0 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_probe_and_ioctl is added in the DPDK_20.0 section, but is expected to be added in the EXPERIMENTAL section of the version map
prev parent reply other threads:[~2023-11-02 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1698949164-20287-1-git-send-email-rahulgupt@linux.microsoft.com>
2023-11-02 17:59 ` qemudev
2023-11-02 18:20 ` checkpatch [this message]
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=20231102182046.187CC120A24@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rahulgupt@linux.microsoft.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).