automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: |WARNING| pw158037 [PATCH v7] mbuf: optimize segment prefree
Date: Thu, 23 Oct 2025 18:19:22 +0200 (CEST)	[thread overview]
Message-ID: <20251023161922.C9CCB1242B8@dpdk.org> (raw)
In-Reply-To: <20251023161851.328258-1-mb@smartsharesystems.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/158037

_coding style issues_


WARNING:TYPO_SPELLING: 'endcode' may be misspelled - perhaps 'encode'?
#202: FILE: lib/mbuf/rte_mbuf_core.h:721:
+ * ^[ndcode
     ^^^^^^^

WARNING:TYPO_SPELLING: 'endcode' may be misspelled - perhaps 'encode'?
#214: FILE: lib/mbuf/rte_mbuf_core.h:733:
+ * ^[ndcode
     ^^^^^^^

WARNING:TYPO_SPELLING: 'endcode' may be misspelled - perhaps 'encode'?
#219: FILE: lib/mbuf/rte_mbuf_core.h:738:
+ * ^[ndcode
     ^^^^^^^

total: 0 errors, 3 warnings, 124 lines checked

  parent reply	other threads:[~2025-10-23 16:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251023161851.328258-1-mb@smartsharesystems.com>
2025-10-23 15:45 ` |SUCCESS| " qemudev
2025-10-23 15:50 ` qemudev
2025-10-23 16:19 ` checkpatch [this message]
2025-10-23 16:43 ` |SUCCESS| pw158037 [PATCH] [v7] " dpdklab
2025-10-23 16:44 ` |PENDING| " dpdklab
2025-10-23 16:48 ` |SUCCESS| " dpdklab
2025-10-23 16:58 ` |PENDING| " dpdklab
2025-10-23 17:00 ` |SUCCESS| " dpdklab
2025-10-23 17:02 ` dpdklab
2025-10-23 17:04 ` |FAILURE| " dpdklab
2025-10-23 17:04 ` |SUCCESS| " dpdklab
2025-10-23 17:04 ` dpdklab
2025-10-23 17:05 ` dpdklab
2025-10-23 17:14 ` |PENDING| " dpdklab
2025-10-23 17:15 ` |SUCCESS| " dpdklab
2025-10-23 17:26 ` dpdklab
2025-10-23 17:47 ` dpdklab
2025-10-23 18:03 ` dpdklab
2025-10-23 18:18 ` dpdklab
2025-10-23 18:22 ` 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=20251023161922.C9CCB1242B8@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).