From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <skori@marvell.com>
Subject: |WARNING| pw155640 [PATCH v3 2/2] ethdev: remove callback checks from fast path
Date: Mon, 4 Aug 2025 09:46:59 +0200 (CEST) [thread overview]
Message-ID: <20250804074659.DCECE125214@dpdk.org> (raw)
In-Reply-To: <20250804074733.55145-2-skori@marvell.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155640
_coding style issues_
WARNING:TYPO_SPELLING: 'performace' may be misspelled - perhaps 'performance'?
#96:
These checks impact data path performace.
WARNING:BAD_SIGN_OFF: Duplicate signature
#103:
Acked-by: Morten Brørup <mb@smartsharesystems.com>
total: 0 errors, 2 warnings, 235 lines checked
next prev parent reply other threads:[~2025-08-04 7:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250804074733.55145-2-skori@marvell.com>
2025-08-04 7:35 ` |SUCCESS| pw155639-155640 " qemudev
2025-08-04 7:40 ` qemudev
2025-08-04 7:46 ` checkpatch [this message]
2025-08-04 9:05 ` |PENDING| pw155639-155640 [PATCH] [v3,2/2] ethdev: remove callback c dpdklab
2025-08-04 9:06 ` |SUCCESS| pw155640 [PATCH v3 2/2] ethdev: remove callback checks from fast path 0-day Robot
2025-08-04 9:08 ` |SUCCESS| pw155639-155640 [PATCH] [v3,2/2] ethdev: remove callback c dpdklab
2025-08-04 9:09 ` dpdklab
2025-08-04 9:10 ` dpdklab
2025-08-04 9:15 ` dpdklab
2025-08-04 9:15 ` |PENDING| " dpdklab
2025-08-04 9:18 ` |SUCCESS| " dpdklab
2025-08-04 9:19 ` dpdklab
2025-08-04 9:31 ` dpdklab
2025-08-04 10:14 ` dpdklab
2025-08-04 10:22 ` dpdklab
2025-08-04 10:32 ` dpdklab
2025-08-04 10:40 ` dpdklab
2025-08-04 10:49 ` dpdklab
2025-08-04 11:08 ` dpdklab
2025-08-04 11:09 ` 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=20250804074659.DCECE125214@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=skori@marvell.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).