automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw153799 [PATCH v2] build: reduce use of AVX compiler flags
Date: Tue, 27 May 2025 18:28:13 +0200 (CEST)	[thread overview]
Message-ID: <20250527162813.31F85125267@dpdk.org> (raw)
In-Reply-To: <20250527162716.319713-1-bruce.richardson@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153799

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#74: 
Depends-on: series-35006 ("doc/linux_gsg: update recommended compiler versions")

total: 0 errors, 1 warnings, 95 lines checked

  parent reply	other threads:[~2025-05-27 16:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250527162716.319713-1-bruce.richardson@intel.com>
2025-05-27 15:57 ` |SUCCESS| " qemudev
2025-05-27 16:01 ` qemudev
2025-05-27 16:28 ` checkpatch [this message]
2025-05-27 17:44 ` 0-day Robot
2025-05-27 23:29 ` |SUCCESS| pw153799 [PATCH] [v2] build: reduce use of AVX compiler fl dpdklab
2025-05-27 23:35 ` dpdklab
2025-05-27 23:44 ` dpdklab
2025-05-27 23:56 ` |PENDING| " dpdklab
2025-05-28  0:20 ` |SUCCESS| " dpdklab
2025-05-28  0:47 ` dpdklab
2025-05-28  0:58 ` dpdklab
2025-05-28  1:37 ` dpdklab
2025-05-28  1:39 ` |PENDING| " dpdklab
2025-05-28  2:33 ` dpdklab
2025-05-28  2:40 ` |WARNING| " dpdklab
2025-05-28  3:32 ` dpdklab
2025-05-28  3:37 ` |SUCCESS| " dpdklab
2025-05-28  5:18 ` dpdklab
2025-05-28  6:15 ` dpdklab
2025-05-28  7:01 ` |WARNING| " dpdklab
2025-05-28  8:03 ` |SUCCESS| " dpdklab
2025-05-28  8:36 ` dpdklab
2025-05-28  9:49 ` |WARNING| " dpdklab
2025-06-03 20:23 ` |SUCCESS| " dpdklab
2025-06-04  3:55 ` 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=20250527162813.31F85125267@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).