From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: |WARNING| pw155364 [PATCH] mbuf: de-inline sanity checking a reinitialized mbuf
Date: Sat, 19 Jul 2025 12:22:04 +0200 (CEST) [thread overview]
Message-ID: <20250719102204.62A8212530F@dpdk.org> (raw)
In-Reply-To: <20250719102315.435921-1-mb@smartsharesystems.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155364
_coding style issues_
WARNING:TYPO_SPELLING: 'ASSSERT' may be misspelled - perhaps 'ASSERT'?
#67:
RTE_ASSSERT(), so they don't depend on RTE_ENABLE_ASSERT.
total: 0 errors, 1 warnings, 238 lines checked
Warning in lib/mbuf/rte_mbuf.c:
Using rte_panic/rte_exit
next prev parent reply other threads:[~2025-07-19 10:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250719102315.435921-1-mb@smartsharesystems.com>
2025-07-19 9:49 ` |SUCCESS| " qemudev
2025-07-19 9:53 ` qemudev
2025-07-19 10:22 ` checkpatch [this message]
2025-07-19 11:15 ` |SUCCESS| pw155364 [PATCH] mbuf: de-inline sanity checking a reiniti dpdklab
2025-07-19 11:19 ` dpdklab
2025-07-19 11:30 ` |PENDING| " dpdklab
2025-07-19 11:30 ` |SUCCESS| " dpdklab
2025-07-19 11:30 ` dpdklab
2025-07-19 11:32 ` |PENDING| " dpdklab
2025-07-19 11:32 ` |SUCCESS| " dpdklab
2025-07-19 11:39 ` |PENDING| " dpdklab
2025-07-19 11:43 ` |SUCCESS| pw155364 [PATCH] mbuf: de-inline sanity checking a reinitialized mbuf 0-day Robot
2025-07-19 11:45 ` |PENDING| pw155364 [PATCH] mbuf: de-inline sanity checking a reiniti dpdklab
2025-07-19 11:46 ` |SUCCESS| " dpdklab
2025-07-19 11:54 ` dpdklab
2025-07-19 12:19 ` |PENDING| " dpdklab
2025-07-19 12:29 ` |SUCCESS| " dpdklab
2025-07-19 12:33 ` dpdklab
2025-07-19 12:49 ` dpdklab
2025-07-19 12:59 ` 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=20250719102204.62A8212530F@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).