automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Thierry Herbelot <thierry.herbelot@6wind.com>
Subject: |WARNING| pw157298 [V2] net/intel/e1000: reduce the optimization level for gcc > 11
Date: Mon,  6 Oct 2025 15:03:12 +0200 (CEST)	[thread overview]
Message-ID: <20251006130312.50057124262@dpdk.org> (raw)
In-Reply-To: <20251006130257.391200-1-thierry.herbelot@6wind.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#102: 
> #0  rte_read32_relaxed (addr=0x1100800e00) at ../sources/lib/eal/include/generic/rte_io.h:290

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

  parent reply	other threads:[~2025-10-06 13:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251006130257.391200-1-thierry.herbelot@6wind.com>
2025-10-06 12:29 ` |SUCCESS| " qemudev
2025-10-06 12:33 ` qemudev
2025-10-06 13:03 ` checkpatch [this message]
2025-10-06 13:31 ` |PENDING| pw157298 [PATCH] [V2] net/intel/e1000: reduce the optimiza dpdklab
2025-10-06 13:35 ` |SUCCESS| " dpdklab
2025-10-06 13:39 ` dpdklab
2025-10-06 13:44 ` |PENDING| " dpdklab
2025-10-06 13:47 ` dpdklab
2025-10-06 13:53 ` dpdklab
2025-10-06 13:55 ` |SUCCESS| " dpdklab
2025-10-06 14:02 ` dpdklab
2025-10-06 14:08 ` |SUCCESS| pw157298 [V2] net/intel/e1000: reduce the optimization level for gcc > 11 0-day Robot
2025-10-06 14:08 ` 0-day Robot
2025-10-06 14:10 ` |SUCCESS| pw157298 [PATCH] [V2] net/intel/e1000: reduce the optimiza dpdklab
2025-10-06 14:11 ` dpdklab
2025-10-06 14:17 ` dpdklab
2025-10-06 14:18 ` dpdklab
2025-10-06 14:22 ` dpdklab
2025-10-06 14:28 ` dpdklab
2025-10-06 14:36 ` dpdklab
2025-10-06 14:47 ` dpdklab
2025-10-06 14:49 ` dpdklab
2025-10-06 15:02 ` 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=20251006130312.50057124262@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=thierry.herbelot@6wind.com \
    /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).