automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Daniel Gregory <daniel.gregory@bytedance.com>
Subject: |WARNING| pw139802 [PATCH] eal/arm: replace RTE_BUILD_BUG on non-constant
Date: Fri,  3 May 2024 11:57:49 +0200 (CEST)	[thread overview]
Message-ID: <20240503095749.5694F122147@dpdk.org> (raw)
In-Reply-To: <20240502142116.63760-1-daniel.gregory@bytedance.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#87: 
  530 | #define RTE_BUILD_BUG_ON(condition) do { static_assert(!(condition), #condition); } while (0)

total: 0 errors, 1 warnings, 31 lines checked

  parent reply	other threads:[~2024-05-03  9:57 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240502142116.63760-1-daniel.gregory@bytedance.com>
2024-05-02 13:57 ` |SUCCESS| " qemudev
2024-05-02 14:01 ` qemudev
2024-05-02 15:24 ` 0-day Robot
2024-05-02 22:13 ` |SUCCESS| pw139802 [PATCH] eal/arm: replace RTE_BUILD_BUG on non-con dpdklab
2024-05-02 22:14 ` dpdklab
2024-05-02 22:15 ` dpdklab
2024-05-02 22:20 ` dpdklab
2024-05-02 22:21 ` dpdklab
2024-05-02 22:21 ` dpdklab
2024-05-02 22:22 ` dpdklab
2024-05-02 22:22 ` dpdklab
2024-05-02 22:22 ` dpdklab
2024-05-02 22:23 ` dpdklab
2024-05-02 22:23 ` dpdklab
2024-05-02 22:24 ` dpdklab
2024-05-02 22:24 ` dpdklab
2024-05-02 22:24 ` dpdklab
2024-05-02 22:25 ` dpdklab
2024-05-02 22:25 ` dpdklab
2024-05-02 22:26 ` dpdklab
2024-05-02 22:26 ` dpdklab
2024-05-02 22:26 ` dpdklab
2024-05-02 22:27 ` dpdklab
2024-05-02 22:27 ` dpdklab
2024-05-02 22:28 ` dpdklab
2024-05-02 22:29 ` dpdklab
2024-05-02 22:29 ` dpdklab
2024-05-02 22:30 ` dpdklab
2024-05-02 22:30 ` dpdklab
2024-05-02 22:31 ` dpdklab
2024-05-02 22:31 ` dpdklab
2024-05-02 22:31 ` dpdklab
2024-05-02 22:32 ` dpdklab
2024-05-02 22:32 ` dpdklab
2024-05-02 22:32 ` dpdklab
2024-05-02 22:32 ` dpdklab
2024-05-02 22:33 ` dpdklab
2024-05-02 22:33 ` dpdklab
2024-05-02 22:33 ` dpdklab
2024-05-02 22:33 ` dpdklab
2024-05-02 22:34 ` dpdklab
2024-05-02 22:34 ` dpdklab
2024-05-02 22:34 ` dpdklab
2024-05-02 22:34 ` dpdklab
2024-05-02 22:35 ` dpdklab
2024-05-02 22:35 ` dpdklab
2024-05-02 22:35 ` dpdklab
2024-05-02 22:37 ` dpdklab
2024-05-02 22:41 ` dpdklab
2024-05-02 22:41 ` dpdklab
2024-05-02 22:44 ` dpdklab
2024-05-02 22:57 ` dpdklab
2024-05-02 22:59 ` dpdklab
2024-05-02 22:59 ` dpdklab
2024-05-02 22:59 ` dpdklab
2024-05-02 22:59 ` dpdklab
2024-05-02 23:00 ` dpdklab
2024-05-02 23:01 ` dpdklab
2024-05-02 23:02 ` dpdklab
2024-05-02 23:02 ` dpdklab
2024-05-02 23:03 ` dpdklab
2024-05-02 23:03 ` dpdklab
2024-05-02 23:04 ` dpdklab
2024-05-02 23:05 ` dpdklab
2024-05-02 23:09 ` dpdklab
2024-05-02 23:12 ` dpdklab
2024-05-02 23:19 ` dpdklab
2024-05-02 23:20 ` dpdklab
2024-05-02 23:26 ` dpdklab
2024-05-02 23:33 ` dpdklab
2024-05-02 23:34 ` dpdklab
2024-05-02 23:35 ` dpdklab
2024-05-02 23:36 ` dpdklab
2024-05-02 23:45 ` dpdklab
2024-05-02 23:58 ` dpdklab
2024-05-03  0:06 ` dpdklab
2024-05-03  0:09 ` dpdklab
2024-05-03  0:45 ` dpdklab
2024-05-03  0:59 ` dpdklab
2024-05-03  1:02 ` dpdklab
2024-05-03  2:00 ` dpdklab
2024-05-03  2:14 ` dpdklab
2024-05-03  8:21 ` |WARNING| pw139802 [PATCH] eal/arm: replace RTE_BUILD_BUG on non-constant checkpatch
2024-05-03  9:50 ` checkpatch
2024-05-03  9:57 ` checkpatch [this message]
2024-05-03 16:01 ` |SUCCESS| pw139802 [PATCH] eal/arm: replace RTE_BUILD_BUG on non-con dpdklab
2024-05-04 23:34 ` dpdklab
2024-05-04 23:38 ` dpdklab
2024-05-04 23:42 ` dpdklab
2024-05-04 23:46 ` dpdklab
2024-05-05  0:05 ` dpdklab
2024-05-06  9:27 ` 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=20240503095749.5694F122147@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=daniel.gregory@bytedance.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).