automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw149784 [PATCH] base/thunderx: fix build with Gcc 15
Date: Fri, 10 Jan 2025 18:27:57 +0100 (CET)	[thread overview]
Message-ID: <20250110172757.B2B48126FD3@dpdk.org> (raw)
In-Reply-To: <20250110172725.540897-1-stephen@networkplumber.org>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#94: 
[2377/3224] Compiling C object drivers/net/thunderx/base/libnicvf_base.a.p/nicvf_mbox.c.o

total: 0 errors, 1 warnings, 0 checks, 168 lines checked

  parent reply	other threads:[~2025-01-10 17:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250110172725.540897-1-stephen@networkplumber.org>
2025-01-10 16:57 ` |SUCCESS| " qemudev
2025-01-10 17:01 ` qemudev
2025-01-10 17:27 ` checkpatch [this message]
2025-01-10 19:45 ` 0-day Robot
2025-01-10 21:00 ` |PENDING| " dpdklab
2025-01-10 21:02 ` |SUCCESS| " dpdklab
2025-01-10 21:02 ` dpdklab
2025-01-10 21:02 ` dpdklab
2025-01-10 21:04 ` |PENDING| " dpdklab
2025-01-10 21:04 ` dpdklab
2025-01-10 21:06 ` |SUCCESS| " dpdklab
2025-01-10 21:07 ` |PENDING| " dpdklab
2025-01-10 21:11 ` |SUCCESS| " dpdklab
2025-01-10 21:14 ` dpdklab
2025-01-10 21:30 ` dpdklab
2025-01-10 21:30 ` dpdklab
2025-01-10 21:50 ` dpdklab
2025-01-10 21:52 ` dpdklab
2025-01-10 21:53 ` dpdklab
2025-01-10 21:55 ` dpdklab
2025-01-10 22:04 ` dpdklab
2025-01-10 22:10 ` dpdklab
2025-01-10 22:47 ` |WARNING| " 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=20250110172757.B2B48126FD3@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).