From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw154860 [PATCH v2] test/argparse: change initialization to workaround LTO
Date: Mon, 30 Jun 2025 16:58:28 +0200 (CEST) [thread overview]
Message-ID: <20250630145828.5353B1252FA@dpdk.org> (raw)
In-Reply-To: <20250630145934.56969-1-stephen@networkplumber.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154860
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#95:
inlined from ‘test_argparse_init_obj’ at ../app/test/test_argparse.c:108:2,
WARNING:TYPO_SPELLING: 'uppper' may be misspelled - perhaps 'upper'?
#105:
and use structure assignment. Also macro should be uppper case.
WARNING:TYPO_SPELLING: 'arrary' may be misspelled - perhaps 'array'?
#153: FILE: app/test/test_argparse.c:94:
+ /* Note: initialization of structure with flexible arrary
total: 0 errors, 3 warnings, 47 lines checked
next prev parent reply other threads:[~2025-06-30 14:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250630145934.56969-1-stephen@networkplumber.org>
2025-06-30 14:25 ` |SUCCESS| " qemudev
2025-06-30 14:30 ` qemudev
2025-06-30 14:58 ` checkpatch [this message]
2025-06-30 16:07 ` |PENDING| pw154860 [PATCH] [v2] test/argparse: change initialization dpdklab
2025-06-30 16:07 ` |SUCCESS| " dpdklab
2025-06-30 16:09 ` |FAILURE| " dpdklab
2025-06-30 16:13 ` |SUCCESS| " dpdklab
2025-06-30 16:16 ` dpdklab
2025-06-30 16:20 ` dpdklab
2025-06-30 16:23 ` |SUCCESS| pw154860 [PATCH v2] test/argparse: change initialization to workaround LTO 0-day Robot
2025-06-30 16:26 ` |PENDING| pw154860 [PATCH] [v2] test/argparse: change initialization dpdklab
2025-06-30 16:48 ` |SUCCESS| " dpdklab
2025-06-30 17:02 ` dpdklab
2025-06-30 17:17 ` dpdklab
2025-06-30 17:18 ` dpdklab
2025-06-30 17:32 ` |PENDING| " dpdklab
2025-06-30 17:36 ` dpdklab
2025-06-30 18:21 ` |SUCCESS| " dpdklab
2025-06-30 18:21 ` dpdklab
2025-06-30 19:22 ` dpdklab
2025-06-30 19:34 ` dpdklab
2025-06-30 19:34 ` dpdklab
2025-06-30 19:34 ` dpdklab
2025-06-30 19:35 ` dpdklab
2025-06-30 19:35 ` dpdklab
2025-06-30 19:35 ` dpdklab
2025-06-30 21:46 ` |WARNING| " dpdklab
2025-06-30 21:46 ` dpdklab
2025-06-30 21:49 ` dpdklab
2025-06-30 23:49 ` |SUCCESS| " dpdklab
2025-07-01 1:00 ` 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=20250630145828.5353B1252FA@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).