From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw158108 [PATCH] mbuf: fix build failure if MBUF_HISTORY_DEBUG enabled
Date: Sat, 25 Oct 2025 00:30:27 +0200 (CEST) [thread overview]
Message-ID: <20251024223027.B4BD21261C0@dpdk.org> (raw)
In-Reply-To: <20251024222946.323662-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/158108
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#103:
219 | MBUF_LOG(ERR, "Failed to register mbuf history dynamic field: %s
",
total: 0 errors, 1 warnings, 8 lines checked
next prev parent reply other threads:[~2025-10-24 22:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251024222946.323662-1-stephen@networkplumber.org>
2025-10-24 21:55 ` |SUCCESS| " qemudev
2025-10-24 22:00 ` qemudev
2025-10-24 22:30 ` checkpatch [this message]
2025-10-24 22:57 ` |PENDING| pw158108 [PATCH] mbuf: fix build failure if MBUF_HISTORY_D dpdklab
2025-10-24 22:59 ` |SUCCESS| " dpdklab
2025-10-24 23:03 ` dpdklab
2025-10-24 23:08 ` |PENDING| " dpdklab
2025-10-24 23:08 ` |WARNING| " dpdklab
2025-10-24 23:15 ` |SUCCESS| " dpdklab
2025-10-24 23:21 ` dpdklab
2025-10-24 23:23 ` dpdklab
2025-10-24 23:23 ` |PENDING| " dpdklab
2025-10-24 23:25 ` dpdklab
2025-10-24 23:54 ` |SUCCESS| " dpdklab
2025-10-25 0:15 ` dpdklab
2025-10-25 0:22 ` |WARNING| " dpdklab
2025-10-25 0:22 ` |FAILURE| pw158108 [PATCH] mbuf: fix build failure if MBUF_HISTORY_DEBUG enabled 0-day Robot
2025-10-25 0:28 ` |SUCCESS| pw158108 [PATCH] mbuf: fix build failure if MBUF_HISTORY_D dpdklab
2025-10-25 0:29 ` dpdklab
2025-10-25 0:43 ` |WARNING| " dpdklab
2025-10-25 0:49 ` |SUCCESS| " dpdklab
2025-10-25 1:56 ` dpdklab
2025-10-25 22:08 ` |PENDING| " dpdklab
2025-10-25 22:24 ` |WARNING| " dpdklab
2025-10-26 5:07 ` |SUCCESS| " 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=20251024223027.B4BD21261C0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).