From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: |WARNING| pw144369 [RFC PATCH v3] mempool: obey configured cache size
Date: Fri, 20 Sep 2024 19:14:23 +0200 (CEST) [thread overview]
Message-ID: <20240920171423.37742121D9E@dpdk.org> (raw)
In-Reply-To: <20240920171350.841532-1-mb@smartsharesystems.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/144369
_coding style issues_
WARNING:TYPO_SPELLING: 'Finallly' may be misspelled - perhaps 'Finally'?
#68:
Finallly, the mempool get and put functions are optimized to only
WARNING:TYPO_SPELLING: 'Variuos' may be misspelled - perhaps 'Various'?
#72:
Variuos drivers accessing the mempool directly have been updated
total: 0 errors, 2 warnings, 732 lines checked
next prev parent reply other threads:[~2024-09-20 17:14 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240920171350.841532-1-mb@smartsharesystems.com>
2024-09-20 16:47 ` |SUCCESS| " qemudev
2024-09-20 16:51 ` qemudev
2024-09-20 17:14 ` checkpatch [this message]
2024-09-20 17:48 ` |FAILURE| " 0-day Robot
2024-09-21 15:40 ` |FAILURE| pw144369 [PATCH] [RFC,v3] mempool: obey configured cache s dpdklab
2024-09-21 15:41 ` dpdklab
2024-09-21 15:42 ` dpdklab
2024-09-21 15:42 ` dpdklab
2024-09-21 15:43 ` dpdklab
2024-09-21 15:44 ` dpdklab
2024-09-21 15:44 ` dpdklab
2024-09-21 15:45 ` dpdklab
2024-09-21 15:47 ` dpdklab
2024-09-21 15:47 ` dpdklab
2024-09-21 15:48 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:49 ` dpdklab
2024-09-21 15:50 ` dpdklab
2024-09-21 15:50 ` dpdklab
2024-09-21 15:50 ` |SUCCESS| " dpdklab
2024-09-21 15:50 ` |FAILURE| " dpdklab
2024-09-21 15:50 ` dpdklab
2024-09-21 15:52 ` |WARNING| " dpdklab
2024-09-21 15:53 ` dpdklab
2024-09-21 15:53 ` |FAILURE| " dpdklab
2024-09-21 15:54 ` dpdklab
2024-09-21 15:54 ` dpdklab
2024-09-21 15:54 ` dpdklab
2024-09-21 15:54 ` dpdklab
2024-09-21 15:58 ` |SUCCESS| " dpdklab
2024-09-21 16:03 ` |FAILURE| " dpdklab
2024-09-21 16:03 ` dpdklab
2024-09-21 16:04 ` |WARNING| " dpdklab
2024-09-21 16:04 ` dpdklab
2024-09-21 16:04 ` |FAILURE| " dpdklab
2024-09-21 16:04 ` dpdklab
2024-09-21 16:04 ` dpdklab
2024-09-21 16:04 ` dpdklab
2024-09-21 16:04 ` |WARNING| " dpdklab
2024-09-21 16:04 ` |FAILURE| " dpdklab
2024-09-21 16:04 ` dpdklab
2024-09-21 16:05 ` dpdklab
2024-09-21 16:06 ` dpdklab
2024-09-21 16:19 ` |SUCCESS| " dpdklab
2024-09-21 16:22 ` dpdklab
2024-09-21 16:25 ` dpdklab
2024-09-21 16:54 ` dpdklab
2024-09-21 18:45 ` |WARNING| " dpdklab
2024-09-23 17:49 ` |SUCCESS| " dpdklab
2024-09-23 21:35 ` 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=20240920171423.37742121D9E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mb@smartsharesystems.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).