From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andre Muezerie <andremue@linux.microsoft.com>
Subject: |WARNING| pw152908 [PATCH] eal: simplify code to avoid Coverity false positive
Date: Mon, 14 Apr 2025 22:29:00 +0200 (CEST) [thread overview]
Message-ID: <20250414202900.259B5124124@dpdk.org> (raw)
In-Reply-To: <1744662518-5433-1-git-send-email-andremue@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152908
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#53:
https://scan4.scan.coverity.com/#/project-view/66295/10075?selectedIssue=461876
total: 0 errors, 1 warnings, 32 lines checked
next prev parent reply other threads:[~2025-04-14 20:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1744662518-5433-1-git-send-email-andremue@linux.microsoft.com>
2025-04-14 19:55 ` |SUCCESS| " qemudev
2025-04-14 20:00 ` qemudev
2025-04-14 20:29 ` checkpatch [this message]
2025-04-14 21:03 ` |PENDING| pw152908 [PATCH] eal: simplify code to avoid Coverity fals dpdklab
2025-04-14 21:03 ` |SUCCESS| " dpdklab
2025-04-14 21:11 ` dpdklab
2025-04-14 21:18 ` dpdklab
2025-04-14 21:20 ` |PENDING| " dpdklab
2025-04-14 21:23 ` |SUCCESS| pw152908 [PATCH] eal: simplify code to avoid Coverity false positive 0-day Robot
2025-04-14 21:23 ` |SUCCESS| pw152908 [PATCH] eal: simplify code to avoid Coverity fals dpdklab
2025-04-14 21:26 ` |PENDING| " dpdklab
2025-04-14 21:26 ` |SUCCESS| " dpdklab
2025-04-14 21:38 ` dpdklab
2025-04-14 21:39 ` dpdklab
2025-04-14 21:48 ` dpdklab
2025-04-14 22:06 ` dpdklab
2025-04-14 22:10 ` dpdklab
2025-04-14 22:12 ` dpdklab
2025-04-14 22:33 ` dpdklab
2025-04-14 22:42 ` dpdklab
2025-04-14 23:23 ` dpdklab
2025-04-15 18:49 ` dpdklab
2025-04-15 19:23 ` 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=20250414202900.259B5124124@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andremue@linux.microsoft.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).