From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw152349 [PATCH] net/intel: remove unnecessary compiler flag for mingw
Date: Wed, 12 Mar 2025 16:56:01 +0100 (CET) [thread overview]
Message-ID: <20250312155601.F21DC123FC4@dpdk.org> (raw)
In-Reply-To: <20250312155458.1395709-1-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152349
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#71:
[1] https://inbox.dpdk.org/dev/CAJFAV8z3qFhT9Vv5xOpLhi74BYAht2YCfL2ffLrmei4hfSG5jg@mail.gmail.com
total: 0 errors, 1 warnings, 0 checks, 49 lines checked
next prev parent reply other threads:[~2025-03-12 15:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250312155458.1395709-1-bruce.richardson@intel.com>
2025-03-12 15:23 ` |SUCCESS| " qemudev
2025-03-12 15:28 ` qemudev
2025-03-12 15:56 ` checkpatch [this message]
2025-03-12 17:05 ` 0-day Robot
2025-03-12 20:47 ` |SUCCESS| pw152349 [PATCH] net/intel: remove unnecessary compiler fl dpdklab
2025-03-12 20:54 ` dpdklab
2025-03-12 20:54 ` dpdklab
2025-03-12 21:05 ` dpdklab
2025-03-12 21:31 ` dpdklab
2025-03-12 21:56 ` |PENDING| " dpdklab
2025-03-12 21:58 ` dpdklab
2025-03-12 21:59 ` |SUCCESS| " dpdklab
2025-03-12 22:10 ` dpdklab
2025-03-12 22:17 ` |PENDING| " dpdklab
2025-03-12 22:20 ` |SUCCESS| " dpdklab
2025-03-12 22:28 ` |PENDING| " dpdklab
2025-03-12 23:00 ` |SUCCESS| " dpdklab
2025-03-12 23:12 ` dpdklab
2025-03-12 23:13 ` dpdklab
2025-03-12 23:13 ` dpdklab
2025-03-12 23:17 ` dpdklab
2025-03-12 23:17 ` dpdklab
2025-03-12 23:23 ` dpdklab
2025-03-12 23:28 ` dpdklab
2025-03-12 23:31 ` dpdklab
2025-03-13 0:07 ` 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=20250312155601.F21DC123FC4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@intel.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).