From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw149783 [PATCH] crypto/cnxk: fix gcc 15 warning
Date: Fri, 10 Jan 2025 18:06:08 +0100 (CET) [thread overview]
Message-ID: <20250110170608.6A5DC126FD3@dpdk.org> (raw)
In-Reply-To: <20250110170603.538756-1-stephen@networkplumber.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/149783
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#95:
inlined from ‘cpt_pdcp_chain_alg_prep’ at ../drivers/crypto/cnxk/cnxk_se.h:1621:11,
total: 0 errors, 1 warnings, 8 lines checked
next prev parent reply other threads:[~2025-01-10 17:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250110170603.538756-1-stephen@networkplumber.org>
2025-01-10 16:35 ` |SUCCESS| " qemudev
2025-01-10 16:39 ` qemudev
2025-01-10 17:06 ` checkpatch [this message]
2025-01-10 17:46 ` |PENDING| " dpdklab
2025-01-10 17:46 ` |SUCCESS| " dpdklab
2025-01-10 17:47 ` dpdklab
2025-01-10 17:47 ` |PENDING| " dpdklab
2025-01-10 17:48 ` |SUCCESS| " dpdklab
2025-01-10 17:51 ` dpdklab
2025-01-10 18:02 ` dpdklab
2025-01-10 18:03 ` dpdklab
2025-01-10 18:07 ` |PENDING| " dpdklab
2025-01-10 18:08 ` |SUCCESS| " dpdklab
2025-01-10 18:15 ` dpdklab
2025-01-10 18:35 ` dpdklab
2025-01-10 18:40 ` dpdklab
2025-01-10 18:44 ` dpdklab
2025-01-10 18:51 ` dpdklab
2025-01-10 18:58 ` |WARNING| " dpdklab
2025-01-10 19:27 ` |SUCCESS| " 0-day Robot
2025-01-10 21:08 ` 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=20250110170608.6A5DC126FD3@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).